Sure enough, there was a /etc/crontab entry to do freshclam, and also one under the crontab for the user clamav.
The reason it wasn't an issue for the other VPS2 account that I did the update on at the same time, was that the other VPS2 also had a duplicate entry to do freshclam, but it was for at a different time interval than the crontab entry for the clamav user.
Hope this helps someone else - i'm still trying to wrap my head around the difference between the root user crontab and the /etc/crontab file and all the other user's cronjobs, but i'm getting closer :)
Matt At 8:15 AM -0600 5/5/05, Scott Wiersdorf said something about:
On Thu, May 05, 2005 at 06:33:54AM -0700, Matt Cohen wrote:Thanks for all the details, but I see the same UID and GID on the non-working system as I do on the working one. I guess this one goes to support.I didn't hear if you checked the permissions on the parent directory of the log file. They need to be writable by clamav also. Scott -- Scott Wiersdorf <scott@xxxxxxxxxxxx> ====================================================================== This is <vps-mail@xxxxxxxxxxxx> <http://www.perlcode.org/lists/> Before posting a question, please search the archives (see above URL).
-- :-:+:-:+:-:+:-:+:-:+:-:+:-:+:-:+:-:+:-:+:-:+:-:+:-:+:-:+:-:+:-:+:-:+:-:+ Matthew I. Cohen http://www.iwbyte.com/ It Won't Byte Web Design & Hosting. Ob. Quote: "Reality is for those email: lists@xxxxxxxxxx people who can't handle Fantasy" ====================================================================== This is <vps-mail@xxxxxxxxxxxx> <http://www.perlcode.org/lists/> Before posting a question, please search the archives (see above URL).