Typo for fail2ban config files in file.locations.html.

This commit is contained in:
Zhang Huangbin 2016-04-28 17:46:21 +08:00
parent be26d5ee45
commit 4b655fb55b
3 changed files with 39 additions and 16 deletions

View File

@ -218,14 +218,27 @@ set `$sa_debug = 1;` in Amavisd config file, then restart Amavisd service.
## Fail2ban
* Main config file is `/etc/fail2ban/jail.local`. All custom settings should be
placed in `/etc/fail2ban/jail.local`, and don't touch `jail.conf`, so that
upgrading Fail2ban binary package won't override your custom settings.
Main config file:
* All filter rules are defined in files under `/etc/fail2ban/filter.d/`.
* Actions are defined in files under `/etc/fail2ban/action.d/`.
* On Linux/OpenBSD, it's `/etc/fail2ban/jail.local`.
* On FreeBSD, it's `/usr/local/etc/fail2ban/jail.local`.
!!! warning
All custom settings should be placed in `jail.local`, and don't touch
`jail.conf`, so that upgrading Fail2ban binary package won't lose/override
your custom settings.
Filters:
* On Linux/OpenBSD, all filters are defined in files under `/etc/fail2ban/filter.d/`.
* On FreeBSD, all filters are defined in files under `/usr/local/etc/fail2ban/filter.d/`.
Ban/Unban actions:
* On Linux/OpenBSD, all actions are defined in files under `/etc/fail2ban/action.d/`.
* On FreeBSD, all filters are defined in files under `/usr/local/etc/fail2ban/action.d/`.
FreeBSD system is `/usr/local/etc/fail2ban/`.
## SOGo Groupware

View File

@ -342,6 +342,7 @@ li { line-height: 26px; }
background: #e7f2fa;
}
.admonition { margin-top: 20px; }
.admonition-title {
font-weight: bold;
display: block;

View File

@ -280,18 +280,27 @@ on Debian/Ubuntu.</p>
<p>SpamAssassin doesn't have a separated log file, to debug SpamAssassin, please
set <code>$sa_debug = 1;</code> in Amavisd config file, then restart Amavisd service.</p>
<h2 id="fail2ban">Fail2ban</h2>
<p>Main config file:</p>
<ul>
<li>
<p>Main config file is <code>/etc/fail2ban/jail.local</code>. All custom settings should be
placed in <code>/etc/fail2ban/jail.local</code>, and don't touch <code>jail.conf</code>, so that
upgrading Fail2ban binary package won't override your custom settings.</p>
</li>
<li>
<p>All filter rules are defined in files under <code>/etc/fail2ban/filter.d/</code>.</p>
</li>
<li>Actions are defined in files under <code>/etc/fail2ban/action.d/</code>.</li>
<li>On Linux/OpenBSD, it's <code>/etc/fail2ban/jail.local</code>.</li>
<li>On FreeBSD, it's <code>/usr/local/etc/fail2ban/jail.local</code>.</li>
</ul>
<div class="admonition warning">
<p class="admonition-title">Warning</p>
<p>All custom settings should be placed in <code>jail.local</code>, and don't touch
<code>jail.conf</code>, so that upgrading Fail2ban binary package won't lose/override
your custom settings.</p>
</div>
<p>Filters:</p>
<ul>
<li>On Linux/OpenBSD, all filters are defined in files under <code>/etc/fail2ban/filter.d/</code>.</li>
<li>On FreeBSD, all filters are defined in files under <code>/usr/local/etc/fail2ban/filter.d/</code>.</li>
</ul>
<p>Ban/Unban actions:</p>
<ul>
<li>On Linux/OpenBSD, all actions are defined in files under <code>/etc/fail2ban/action.d/</code>.</li>
<li>On FreeBSD, all filters are defined in files under <code>/usr/local/etc/fail2ban/action.d/</code>.</li>
</ul>
<p>FreeBSD system is <code>/usr/local/etc/fail2ban/</code>.</p>
<h2 id="sogo-groupware">SOGo Groupware</h2>
<ul>
<li>Main config file is <code>/etc/sogo/sogo.conf</code>.</li>