From: Yaroslav H. <li...@on...> - 2006-03-22 22:38:32
|
=46rom the first look at logwatch code: the only place where it seems to load conf files from /etc/logwatch (on debian at least) is here: # Find out what logfiles are defined... opendir(LOGFILEDIR, $BaseDir . "/default.conf/logfiles") or die $BaseDir . = "/default.conf/logfiles/, no such direc tory.\n"; while (defined($ThisFile =3D readdir(LOGFILEDIR))) { unless (-d $BaseDir . "/default.conf/logfiles/" . $ThisFile) { my $ThisLogFile =3D $ThisFile; if ($ThisLogFile =3D~ s/\.conf$//i) { push @AllLogFiles, $ThisLogFile; @ReadConfigNames =3D (); @ReadConfigValues =3D (); @Separators =3D (); push (@Separators, scalar(@ReadConfigNames)); ReadConfigFile("$BaseDir/default.conf/logfiles/" . $ThisFile, ""); push (@Separators, scalar(@ReadConfigNames)); ReadConfigFile("$BaseDir/dist.conf/logfiles/" . $ThisFile, ""); push (@Separators, scalar(@ReadConfigNames)); ReadConfigFile("$ConfigDir/conf/logfiles/" . $ThisFile, ""); push (@Separators, scalar(@ReadConfigNames)); ReadConfigFile("$ConfigDir/conf/override.conf", "logfiles/$ThisLog= File"); =2E.... So, if there is no fail2ban.conf under $BaseDir . "/default.conf/logfiles/"= , then it never gets read from /etc/logwatch seems to me... yikes...=20 On Wed, 22 Mar 2006, Rarig, Harry wrote: > Ben, > Try=20 > logwatch --debug Med --print --service fail2ban > or > logwatch --debug High --print --service fail2ban > and see if that helps identify the root cause of your problem. > Cheers! > -----Original Message----- > From: Benjamin Donnachie [mailto:ben...@py...] > Sent: Wednesday, March 22, 2006 3:37 PM > To: Rarig, Harry > Cc: fai...@li... > Subject: Re: [Fail2ban-users] Add fail2ban to your logwatch daily report > Rarig, Harry wrote: > > Here they are guyz...knock yerselves out! ;-) > > If you are running Fedora Core 3, you can untar these directly from "/"= into the correct logwatch directory locations. > Many thanks! > I'm using the cAos distro with Logwatch 7.1 and the files needed to be > installed under /etc/logwatch. Unfortunately, it keeps failing with an > error about a file even though it exists: > # /usr/sbin/logwatch --print --service fail2ban > *** Error: There is no logfile defined. Do you have a > /etc/logwatch/conf/logfiles/fail2ban.conf file ? > # ls /etc/logwatch/conf/logfiles/fail2ban.conf > /etc/logwatch/conf/logfiles/fail2ban.conf > I should be catching up on work at the moment, so I'll look into it later. > Take care, > Ben > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting langua= ge > that extends applications into web and mobile media. Attend the live webc= ast > and join the prime developer group breaking into this new coding territor= y! > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=110944&bid$1720&dat=121642 > _______________________________________________ > Fail2ban-users mailing list > Fai...@li... > https://lists.sourceforge.net/lists/listinfo/fail2ban-users --=20 .-. =3D------------------------------ /v\ ----------------------------=3D Keep in touch // \\ (yoh@|www.)onerussian.com Yaroslav Halchenko /( )\ ICQ#: 60653192 Linux User ^^-^^ [175555] |