What might be happening is two different apps with two different permissions are writing to the files. when the second app writes to the files, its permissions keep the first app (freshclam) from writing to the logs. On Mon, Sep 22, 2008 at 12:16 PM, Carlos Williams <[EMAIL PROTECTED]>wrote:
> Hmmm, something is very strange here because with no changes made to > any config or permissions modified, I am now able to run 'freshclam' > with out any errors as I was having in my 1st example. All I simply > did was 'restart' the daemon running 'freshclam': > > mail:/etc# /etc/init.d/clamav-freshclam restart > Stopping ClamAV virus database updater: freshclam. > Starting ClamAV virus database updater: freshclam. > mail:/etc# freshclam > ClamAV update process started at Mon Sep 22 13:13:42 2008 > main.cld is up to date (version: 48, sigs: 399264, f-level: 35, builder: > sven) > daily.cld is up to date (version: 8308, sigs: 33402, f-level: 35, > builder: arnaud) > > What do you guys thing? Is my system still configured incorrectly? I > know its working now but chances are I will have this problem all over > again shortly and I don't know the cause of this. If it was incorrect > configuration, I would like to resolve this and understand it. Any > help is greatly appreciated. If I need to post anything else to help > better understand what is going on. > > Thanks all! > _______________________________________________ > Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net > http://www.clamav.net/support/ml > -- http://www.volatileminds.net _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
