Todd Lyons wrote:
> 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.
Or just use clamscan --debug?
--
Matthew.van.Eerde (at) hbinc.com 805.964.4554 x902
Hispanic Business Inc./HireDiversity.com Software Engineer
perl -e"map{y/a-z/l-za-k/;print}shift" "Jjhi pcdiwtg Ptga wprztg,"
_______________________________________________
http://lurker.clamav.net/list/clamav-users.html
