From: Benjamin D. <ben...@py...> - 2006-03-22 23:06:19
|
Yaroslav Halchenko wrote: > I observed the weird logwatch behavior, as Ben reported, that even > though file is present under /etc/logwatch/conf/logfiles/fail2ban.conf > logwatch says that it is not there... since at the moment I was anxious > to make a rule for logwatch, not to fix logwatch problems, I just > installed fail2ban scripts system-wide. Ah-ha! I've not installed them system wide and it seems much happier now! :-) # /usr/sbin/logwatch --print --service fail2ban --range all ################### LogWatch 7.1 (11/12/05) #################### Processing Initiated: Wed Mar 22 23:03:01 2006 Date Range Processed: all Detail Level of Output: 5 Type of Output: unformatted Logfiles for Host: kevin.pythagoras.no-ip.org ################################################################## --------------------- fail2ban-messages Begin ------------------------ Banned services with Fail2Ban: Apache: 87.74.28.38 (host-87-74-28-38.bulldogdsl.com) SSH: 87.74.28.38 (host-87-74-28-38.bulldogdsl.com) ---------------------- fail2ban-messages End ------------------------- ###################### LogWatch End ######################### Many thanks! :-) Ben |