Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- # Fail2Ban main configuration file
- #
- # Comments: use '#' for comment lines and ';' (following a space) for inline comments
- #
- # Changes: in most of the cases you should not modify this
- # file, but provide customizations in fail2ban.local file, e.g.:
- #
- # [Definition]
- # loglevel = 4
- #
- [Definition]
- # Option: loglevel
- # Notes.: Set the log level output.
- # 1 = ERROR
- # 2 = WARN
- # 3 = INFO
- # 4 = DEBUG
- # Values: [ NUM ] Default: 1
- #
- loglevel = 4
- # Option: logtarget
- # Notes.: Set the log target. This could be a file, SYSLOG, STDERR or STDOUT.
- # Only one log target can be specified.
- # If you change logtarget from the default value and you are
- # using logrotate -- also adjust or disable rotation in the
- # corresponding configuration file
- # (e.g. /etc/logrotate.d/fail2ban on Debian systems)
- # Values: [ STDOUT | STDERR | SYSLOG | FILE ] Default: STDERR
- #
- logtarget = /var/log/fail2ban.log
- # Option: socket
- # Notes.: Set the socket file. This is used to communicate with the daemon. Do
- # not remove this file when Fail2ban runs. It will not be possible to
- # communicate with the server afterwards.
- # Values: [ FILE ] Default: /var/run/fail2ban/fail2ban.sock
- #
- socket = /var/run/fail2ban/fail2ban.sock
- # Option: pidfile
- # Notes.: Set the PID file. This is used to store the process ID of the
- # fail2ban server.
- # Values: [ FILE ] Default: /var/run/fail2ban/fail2ban.pid
- #
- pidfile = /var/run/fail2ban/fail2ban.pid
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement