Mcafee autoupdate revisited
Professional Investments Investor Services
info at pro-invest.ca
Thu Jun 12 20:38:25 IST 2003
I left this for a week to see if the usual Wednesday dat would get updated
by cron.hourly/update_virus_scanners. In my cron system logs, I see that it
does indeed (run-parts >/etc/cron.hourly , however the dat has not been
updated. If I run the command as described in your post everything goes as
prescribed. Where else can I look for any possible errors etc? Has anyone
else had any issues?
IS Tech Support
Professional Investments Inc.
From: Julian Field [mailto:mailscanner at ecs.soton.ac.uk]
Sent: Friday, June 06, 2003 10:13 AM
To: info at pro-invest.ca
Cc: mailscanner at jiscmail.ac.uk
Subject: Re: Mcafee autoupdate revisited
Try running /usr/lib/MailScanner/mcafee-autoupdate and see if it says
anything useful (or posts anything useful in your maillog).
At 14:32 06/06/2003, you wrote:
>Sorry to badger this one, but I do not believe my autoupdate is working
>correctly. I have recently upgraded to 4.21-9, have removed the previous
>cron job that I had been calling and am relying on the rpm installed
>update_virus_scanners that is implemented in my cron.hourly directory. In
>system log I can see that 04:01:01 pilx CROND: (root) CMD (run-parts
>/etc/cron.hourly) runs and then no subsequent errors however yesterday upon
>reading more regarding bugbear.b I checked my latest dat file and it had
>been upgraded to mcafee's release on June 5th. Should I be looking
>for an error? If you could please direct me to some things to check that
>would be greatly appreciated.
>IS Tech Support
>Professional Investments Inc.
MailScanner thanks transtec Computers for their support
More information about the MailScanner