syslog not working?

Kevin Spicer kevins at BMRB.CO.UK
Sun May 4 20:51:40 IST 2003

David, you got me a bit worried (I made some small changes to the syslog
code in clamav-autoupdate, which Julian kindly merged into 4.20), but
I've just checked by upgrading my home machine from 4.10 to 4.20-3 and
it seems to be working fine.

Which version of Clam are you using (any of the 'stable' releases should
give you 'ClamAV Updated' under all circumstances, whereas any of the
snapshot releases should give you a message conditional on Clam's exit
status).  I don't _think_ its anything I've done, since my changes
should write something, no matter what happens.

I don't know what your logging set up is (my info & error go to
different files) so it might be worth mentioning that the new autoupdate
script logs with severity error rather than info when something goes

On Sun, 2003-05-04 at 19:06, David While wrote:

I upgraded today from MS 4-10 to MS 4-20-3 I also use ClamAV. When the
hourly update check is performed the syslog calls in clamav-autoupdate
don't appear to be working - there is no output from the script in the
maillog file. I have checked the syslog settings and all syslog calls
mail are logged. The calls in the update-virus-scanners do work.

I am running RH7.3 and perl 5.6.1

Any ideas??

David While
Technical Development Manager
Faculty of Computing, Information & English
University of Central England
Tel: 0121 331 6211

BMRB International
+44 (0)20 8566 5000
This message (and any attachment) is intended only for the
recipient and may contain confidential and/or privileged
material.  If you have received this in error, please contact the
sender and delete this message immediately.  Disclosure, copying
or other action taken in respect of this email or in
reliance on it is prohibited.  BMRB International Limited
accepts no liability in relation to any personal emails, or
content of any email which does not directly relate to our

More information about the MailScanner mailing list