That could be it. If clamav opens the log file initially as root, but when it receives the HUP signal it may be trying as the clam user.
You're right. Petr: the solution to your problem is to change the owner of the log file so clamd is able to open it for r/w.
Doesnt help.
[EMAIL PROTECTED] clamav]# ll total 15 drwxr-xr-x 2 clamav clamav 1024 Feb 2 22:58 . drwxr-xr-x 14 root root 2048 Feb 2 21:33 .. -rw-r----- 1 clamav clamav 11399 Feb 2 22:33 clamd.log [EMAIL PROTECTED] clamav]# mv clamd.log clamd.log.0 [EMAIL PROTECTED] clamav]# kill -SIGHUP `cat /var/run/clamav/clamd.pid` [EMAIL PROTECTED] clamav]# ll total 15 drwxr-xr-x 2 clamav clamav 1024 Feb 2 22:58 . drwxr-xr-x 14 root root 2048 Feb 2 21:33 .. -rw-r----- 1 clamav clamav 11515 Feb 2 22:59 clamd.log.0 # tac clamd.log.0 |more Mon Feb 2 22:59:06 2004 -> ERROR: accept() failed. Mon Feb 2 22:59:06 2004 -> SIGHUP catched: log file re-opened. Mon Feb 2 22:33:49 2004 -> SelfCheck: Database status OK. Mon Feb 2 21:33:12 2004 -> SelfCheck: Database status OK.
------------------------------------------------------- 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
