On Dec 12, 2009, at 11:12 PM, Dennis Peterson wrote: > Just a guess but I think the user that clam runs as does not have permission > to > create a new file in /var/log/clamav after rotate has removed it. When clam > first starts it is often started as user root and then becomes the configured > user. As root it can create a log file on any local file system. If so a cure > is to have the postrotate touch a file and set appropriate permissions before > telling clamav to reload.
I have "create 640 clamav clamav" in the logrotate script, so that should be creating the file and setting the appropriate permissions.. That, I thought, should be enough. But even if I run reload outside of logrotate, when the existing log file is still in place, I get the failed message as well. Thus my confusion. > dp -- Jason 'XenoPhage' Frisvold xenopha...@gmail.com http://blog.godshell.com _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
