I am using logrotate to rotate my clamd logs. I have an entry called "clam" in /etc/logrotate.d which looks like this:
/var/log/clam/clam*.log { sharedscripts postrotate /bin/kill `/usr/bin/cat /var/run/clamd/clamd.pid` 2>/dev/null /usr/local/sbin/clamd endscript }
If I don't kill clamd, it keeps writing to the old log.
When this runs, the clam daemon dies.
I've tried killall -HUP, but it doesn't work (presumably an issue with ownership of the process). I've also tried a sleep between the two commands to give clamd a chance to die.
I have a cron job which "rescues" clamd if it dies, but it's not a very elegant way of doing it.
Any suggestions as to how I can get this working?
Yes . It is known issue. I reported it many times in last 6 month, but developers
ignores it. Log rotating never worked.
Petr
------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
