ClamAV log problem - Solved!!!

[Julian Field]

You need to wrap that call inside an eval like this

eval { Sys::Syslog::setlogsock('unix'); }; # This may fail!

as it won't be legal on all systems.
I've added this to the distribution. The line above is an exact copy of
what is in Log.pm.

At 00:59 27/06/2003, you wrote:
>I was able to track down my ClamAV logging problem.  Sys::Syslog was not
>working in the clamav-autoupdate script.  I had to add the following line
>to the file:
>
>Sys::Syslog::setlogsock('unix');
>
>Once that was done the proper logging to syslog occurred.  I don't know
>why others aren't having this problem since I thought I had a "vanilla"
>Redhat 7.3 install???  I'm using the rpm of MailScanner 4.22-3 and ClamAV
>0.60.
>
>This is what I was getting...
>Jun 25 17:06:13 tiger update.virus.scanners: Found clamav installed
>Jun 25 17:06:13 tiger update.virus.scanners: Updating clamav
>Jun 25 17:06:14 tiger update.virus.scanners: Found f-prot installed
>Jun 25 17:06:14 tiger update.virus.scanners: Updating f-prot
>Jun 25 17:06:15 tiger F-Prot autoupdate[27175]: F-Prot did not need updating.
>
>This is what I now get with the additional line above...
>Jun 26 19:41:34 tiger update.virus.scanners: Found clamav installed
>Jun 26 19:41:34 tiger update.virus.scanners: Updating clamav
>Jun 26 19:41:35 tiger ClamAV-autoupdate[17991]: ClamAV did not need updating
>Jun 26 19:41:35 tiger update.virus.scanners: Found f-prot installed
>Jun 26 19:41:35 tiger update.virus.scanners: Updating f-prot
>Jun 26 19:41:35 tiger F-Prot autoupdate[17999]: F-Prot did not need updating.
>
>--
>Gerry
>
>"The lyfe so short, the craft so long to learne"  Chaucer

--
Julian Field
www.MailScanner.info
MailScanner thanks transtec Computers for their support