mirror of https://github.com/fail2ban/fail2ban
replaced `log` with `logpath` - makes an example more reliable
parent
f6a62bf429
commit
344368a2ab
|
@ -11,10 +11,10 @@ Instead, you'll write a new file having `.local` extension. For example any valu
|
|||
So for example if original `.conf` file contains:
|
||||
```
|
||||
[DEFAULT]
|
||||
log = /path/to/log
|
||||
logpath = /path/to/log
|
||||
|
||||
[section1]
|
||||
log = /other/path
|
||||
logpath = /other/path
|
||||
enabled = true
|
||||
|
||||
[section2]
|
||||
|
@ -23,10 +23,10 @@ enabled = true
|
|||
And you'll create a `.local` file contains:
|
||||
```
|
||||
[DEFAULT]
|
||||
log = /my-path/to/log
|
||||
logpath = /my-path/to/log
|
||||
```
|
||||
The value of parameter `log` in `section1` will be still `/other/path`.<br/>
|
||||
But value of parameter `log` in `section2` will be changed to `/my-path/to/log` (because it was not specified in section self, and new default value will be used).
|
||||
The value of parameter `logpath` in `section1` will be still `/other/path`.<br/>
|
||||
But value of parameter `logpath` in `section2` will be changed to `/my-path/to/log` (because it was not specified in section self, and new default value will be used).
|
||||
|
||||
***
|
||||
**[Q]** Which configurations are necessary to let fail2ban protect a service?<br/>
|
||||
|
|
Loading…
Reference in New Issue