ok -- decided to just change upstream (although there is no logrotate
script shipped by default), so ended up with
# If you change logtarget from the default value and you are
# using logrotate -- also adjust or disable rotation in the
# corresponding configuration file
On Fri, 2013-01-04 at 10:38 -0500, Yaroslav Halchenko wrote:
> sorry that you spend the time elaborating an alternative solution
No worries :)
> arghm -- we forgotten about the elephant(s) ;)
*G*
> so -- the best resolution might be -- DOCUMENTATION in
> /etc/fail2ban/fail2ban.conf
Jep =)
> ma
On Fri, 04 Jan 2013, Christoph Anton Mitterer wrote:
> > fail2ban-client get logtarget | sed -ne '$s/^[-` ]*//gp'
> Damn... I'm so blind... reading several times over these -client options
> and even get logtarget... but not realising that this was exactly what I
> wanted...
sorry that you spend
Hey.
On Thu, 2013-01-03 at 22:41 -0500, Yaroslav Halchenko wrote:
> but what about just adding a command to the client e.g.
>
> fail2ban-client touch logtarget
>
> which would be passed to the server to do the needed action (i.e. if
> logging is done to a file): server.setLogTarget(server.getLo
On Fri, 04 Jan 2013, Christoph Anton Mitterer wrote:
> fail2ban's logrotate config file (/etc/logrotate.d/fail2ban) unconditionally
> overwrites fail2bans logtarget to /var/log/fail2ban.log during the postrotate
> phase.
> So when a user has modified the logtarget in /etc/fail2ban/fail2ban.conf
>
Package: fail2ban
Version: 0.8.6-2
Severity: normal
Tags: patch
Hi.
fail2ban's logrotate config file (/etc/logrotate.d/fail2ban) unconditionally
overwrites fail2bans logtarget to /var/log/fail2ban.log during the postrotate
phase.
So when a user has modified the logtarget in /etc/fail2ban/fail2b
6 matches
Mail list logo
