This website requires JavaScript.
Explore
关于
Help
Register
Sign In
github
/
fail2ban
mirror of
https://github.com/fail2ban/fail2ban
Watch
1
Star
0
Fork
You've already forked fail2ban
0
Code
Issues
Releases
Wiki
Activity
80b1007a8f
fail2ban
/
files
/
fail2ban-openrc.conf
3 lines
78 B
Plaintext
Raw
Normal View
History
Unescape
Escape
files/fail2ban-openrc.conf: remove hard-coded paths. There were two paths mentioned in comments in the fail2ban OpenRC conf file, but those paths aren't guaranteed to be correct (until/unless we integrate the conf file with the build system). The first comment referenced the physical location of the associated init script, and in my opinion is not useful to an end user in the first place. It has been removed: OpenRC users know what this file is for, there's no reason to repeat it in a comment. The second comment contained an absolute path to fail2ban-client, and I've removed the leading path components because "fail2ban-client" is generally run from your $PATH.
2018-07-15 13:11:53 +00:00
# For available options, plase run "fail2ban-client -h".
files/fail2ban-openrc.conf: remove a commented example setting. Our OpenRC conf file already tells users how to find the available options that can be placed in the FAIL2BAN_OPTIONS variable, so having a specific example of, FAIL2BAN_OPTIONS="-x" doesn't provide much more information. In fact, it makes you wonder why it's there in the first place: does the init script have some kind of problem with stale sockets? It used to, but that problem has been fixed. This commit removes the redundant example.
2018-07-15 13:17:29 +00:00
#FAIL2BAN_OPTIONS=""