Ignore, after further exploration I realized that the ExcludePath still goes through the files, it just doesn't actually scan them.
Scott Mohnkern On Thu, Oct 22, 2009 at 1:28 PM, Scott Mohnkern <[email protected]> wrote: > I thought I'd gotten a handle on this, but it seems to be a moving target: > I'm running ClamAV 0.95.2/9926/Thu Oct 22 05:10:50 2009 > > > In /etc/clamd.conf I have the following line: > > ExcludePath ^/data/fxa/ > > When I type: > > [r...@am2-nhdr fxa]# clamdscan /data/fxa/temp.txt > > I get: > > /data/fxa/temp.txt: OK > > > > Since there's been a bug on this on whether there needs to be a leading > slash, I tried changing /etc/clamd.conf so it contained the following; > > ExcludePath ^//data/fxa/ > > did the same thing: > > [r...@am2-nhdr fxa]# clamdscan /data/fxa/temp.txt > /data/fxa/temp.txt: OK > > ----------- SCAN SUMMARY ----------- > Infected files: 0 > Time: 0.033 sec (0 m 0 s) > > > Has anyone gotten ExcludePath to work in a /etc/clamd.conf file with > version 0.95.2/9926? > > > Scott > > > > > Scott Mohnkern > > _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
