I retrieve the r4944 version via svn. When using ExcludePath ^/sys/ it
behaved as expected.
Thanks for the help.
Scott
On Fri, Mar 13, 2009 at 3:03 PM, Török Edwin wrote:
> On 2009-03-13 20:22, Scott Mohnkern wrote:
> > Okay, here's what I did:
> >
> > clamd.conf entry: ExcludePath ^/sys/
>
On 2009-03-13 20:22, Scott Mohnkern wrote:
> Okay, here's what I did:
>
> clamd.conf entry: ExcludePath ^/sys/
> clamdscan /sys : Tried to scan /sys
>
> clamd.conf entry: ExcludePath ^//sys/
> clamdscan /sys : Tried to scan /sys
>
> Where can I get r4944?
Run this command (you'll the subversion
Okay, here's what I did:
clamd.conf entry: ExcludePath ^/sys/
clamdscan /sys : Tried to scan /sys
clamd.conf entry: ExcludePath ^//sys/
clamdscan /sys : Tried to scan /sys
Where can I get r4944?
Scott
On Fri, Mar 13, 2009 at 1:53 PM, Török Edwin wrote:
> On 2009-03-13 19:48, Scott Mohnker
On 2009-03-13 19:48, Scott Mohnkern wrote:
> Interesting, here's what I did:
>
>
> I commented out every single entry in clamd.conf that was an ExcludePath
>
> Restarted clamd
>
> Ran
>
> clamdscan /proc
>
/proc is always excluded on Linux based on the device returned by stat().
Does it work i
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 E
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 cl
Hmm, tried both (one at a time) and neither worked).
Scott
On Fri, Mar 13, 2009 at 1:25 PM, Dennis Peterson wrote:
> Scott Mohnkern wrote:
> > Tried having just:
> >
> > ExcludePath ^/sys/
> >
> >
> > restarted clamd, and then ran clamdscan /sys
> >
> > still is trying to scan the directory.
>
Scott Mohnkern wrote:
> Tried having just:
>
> ExcludePath ^/sys/
>
>
> restarted clamd, and then ran clamdscan /sys
>
> still is trying to scan the directory.
>
> Scott
In the Feb post Thomasz recommended using two slashes as a work-around. Your
original post had both a single and a double
oh and;
ClamAV 0.95rc1/9101/Thu Mar 12 11:30:26 2009
Scott
On Fri, Mar 13, 2009 at 1:04 PM, Dennis Peterson wrote:
> Scott Mohnkern wrote:
> > I recently put .95 on an Ubuntu box, and ExcludePath in clamd.conf
> doesn't
> > seem to be working right.
> >
> > Here's the lines from /usr/local/etc
Tried having just:
ExcludePath ^/sys/
restarted clamd, and then ran clamdscan /sys
still is trying to scan the directory.
Scott
On Fri, Mar 13, 2009 at 1:04 PM, Dennis Peterson wrote:
> Scott Mohnkern wrote:
> > I recently put .95 on an Ubuntu box, and ExcludePath in clamd.conf
> doesn't
>
Scott Mohnkern wrote:
> I recently put .95 on an Ubuntu box, and ExcludePath in clamd.conf doesn't
> seem to be working right.
>
> Here's the lines from /usr/local/etc/clamd.conf for the ExcludePath
>
> ExcludePath ^/proc/
> ExcludePath ^/sys/
> ExcludePath ^//sys/
> ExcludePath ^/tmp/
>
>
> I
I recently put .95 on an Ubuntu box, and ExcludePath in clamd.conf doesn't
seem to be working right.
Here's the lines from /usr/local/etc/clamd.conf for the ExcludePath
ExcludePath ^/proc/
ExcludePath ^/sys/
ExcludePath ^//sys/
ExcludePath ^/tmp/
I realized that there was some question about wh
12 matches
Mail list logo
