Odhiambo Washington wanted us to know: >> Please, set the "Debug" flag in your clamd.conf, rescan the sample, and send >> us the logs. >I cannot do that on the box where this phenomena is manifesting itself >because it's a production box, processing large volumes of mail. I'll
Very quickly, do these: 1) Edit /etc/clamd.conf, uncommenting the Debug option. 2) clamscan the file 3) Edit /etc/clamd.conf, commenting the Debug option. The running clamd process will never read the Debug setting since it doesn't get restarted. clamscan doesn't use the clamd daemon, so you accomplish all that is asked without having to potentially damage the flow of mail across your machine. -- Regards... Todd They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. --Benjamin Franklin Linux kernel 2.6.11-6mdksmp 3 users, load average: 1.27, 1.14, 0.84 _______________________________________________ http://lurker.clamav.net/list/clamav-users.html
