Interesting, here's what I did:
I commented out every single entry in clamd.conf that was an ExcludePath Restarted clamd Ran clamdscan /proc It came back with /proc: OK ----------- SCAN SUMMARY ----------- Infected files: 0 Time: 0.454 sec (0 m 0 s) Then I went back and uncommented the ExcludePath ^/proc/ line, restarted clamd, and got: mohnk...@casa-scott:/usr/local/etc$ sudo clamdscan /proc /proc: OK ----------- SCAN SUMMARY ----------- Infected files: 0 Time: 0.476 sec (0 m 0 s) I'd expect that the former one should have taken a lot longer. On Fri, Mar 13, 2009 at 1:41 PM, Dennis Peterson <denni...@inetnw.com>wrote: > Scott Mohnkern wrote: > > Hmm, tried both (one at a time) and neither worked). > > > > Scott > > > > I wonder if it is the clamdscan response that is the problem. Try > commenting out > the exclude statements and run clamdscan on /proc and see what it looks > like > compared to having it excluded when runninc clamdscan. > > dp > _______________________________________________ > Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net > http://www.clamav.net/support/ml > -- Scott Mohnkern _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
