Really nobody knows an answer to this?
I have found a solution on qmail list :
>>> Jeremy Kitchen wrote: >>> >>> there's no reason to patch clamav to have clamd log to stderr. >>> >>> in clamav.conf: >>> LogFile /dev/stdout >>> LogFileUnlock >>> >>> works on every system I've ever installed it on. >> >> Mine runs as the qscand user (started as root, though) works fine. >> >> http://scriptkitchen.com/qmail/clamav.conf >> >> -Jeremy >
Ahh, you're right. I invoked it with a "setuidgid qscanq" wrapper, and that was what was preventing proper logging. Take that out, make sure the config has the "User qscanq" line, and it works perfectly. Thanks for the tip!
~Kyle
Thanks anyway and have a nice day,
Andrej.
-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
_______________________________________________
Clamav-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/clamav-users
