Logwatch 7.3.6 Bug?

Hello Kirk,

I just upgraded to Logwatch 7.3.6 and noticed something that seems to be
a bug which did not exist in the previous 5.x version I was running.  

I run Logwatch on a central Syslog server and use a simple for loop in a
script to parse each hosts log files.  This seems to work well with one
caveat: On some hosts, the cron section seems to include commands from
the hosts on which Logwatch is run.  To put it another way, the wrong
information is in some reports.  I thought it might be a timing issue so
I introduced a sleep of 5 and then 10 seconds in the loop, but that
didn't help.  I tried the --splithosts option but that didn't help,
either.  Finally, searching Google didn't reveal any answers.  I was
hoping you could shed some light on this.  

Here's the loop if it makes a difference:

for i in $sachosts; do
  /usr/sbin/logwatch --logdir $saclwloc/$i --hostname $i --save
$archdir/$ymd/$i.logwatch.$ymd
done

$sachosts are the hosts
$saclwloc is the base location for each host's logs on the syslog server
The other variables are probably self-explanatory

Thanks for a great product and I look forward to hearing from you.

Best regards,
Michael Starks, CISSP, GSNA
Sr. Security Administrator
Preferred Care
(585)327-2329
PGP Key ID: 0x7155D49F


Confidentiality Notice:
The information contained in this electronic message is intended for the exclusive use of the individual or entity named above and may contain privileged or confidential information.  If the reader of this message is not the intended recipient or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that dissemination, distribution or copying of this information is prohibited.  If you have received this communication in error, please notify the sender immediately by telephone and destroy the copies you received.

_______________________________________________
Logwatch-Devel mailing list
[email protected]
http://www2.list.logwatch.org:81/mailman/listinfo/logwatch-devel