Török Edvin wrote:
On 11/26/06, Dennis Peterson <[EMAIL PROTECTED]> wrote:
Root isn't feeding files to clamd - it is feeding paths to files to
clamd. At least that is what happens here.
To have root feed files to clamd, try:
$ cat | clamdscan -
This adds complexity and defeats any intende
René Berber wrote the following on 11/26/2006 1:26 PM -0800:
> Bill Landry wrote:
>
> > Erez Epstein wrote the following on 11/26/2006 1:24 AM -0800:
> >> Hello everybody,
> >>
> >>
> >> i have set up clamscan to scan all of the server using cron daily
> >> ( /usr/local/bin/clamscan -r -i --exclud
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bill Landry wrote:
> Erez Epstein wrote the following on 11/26/2006 1:24 AM -0800:
>> Hello everybody,
>>
>>
>> i have set up clamscan to scan all of the server using cron daily
>> ( /usr/local/bin/clamscan -r -i --exclude-dir=/sys --no-summary / )
>
On 11/26/06, Dennis Peterson <[EMAIL PROTECTED]> wrote:
Root isn't feeding files to clamd - it is feeding paths to files to
clamd. At least that is what happens here.
To have root feed files to clamd, try:
$ cat | clamdscan -
You'll need the clamdscan from 0.90rc2, (or cvs) for fd-passing t
Bill Landry wrote:
Dennis Peterson wrote the following on 11/26/2006 12:34 PM -0800:
Bill Landry wrote:
Dennis Peterson wrote the following on 11/26/2006 12:11 PM -0800:
Bill Landry wrote:
Erez Epstein wrote the following on 11/26/2006 1:24 AM -0800:
Hello everybody,
i have set up clamscan
Dennis Peterson wrote the following on 11/26/2006 12:34 PM -0800:
> Bill Landry wrote:
>> Dennis Peterson wrote the following on 11/26/2006 12:11 PM -0800:
>>> Bill Landry wrote:
Erez Epstein wrote the following on 11/26/2006 1:24 AM -0800:
> Hello everybody,
>
>
> i have set u
Bill Landry wrote:
Dennis Peterson wrote the following on 11/26/2006 12:11 PM -0800:
Bill Landry wrote:
Erez Epstein wrote the following on 11/26/2006 1:24 AM -0800:
Hello everybody,
i have set up clamscan to scan all of the server using cron daily
( /usr/local/bin/clamscan -r -i --exclude-
Dennis Peterson wrote the following on 11/26/2006 12:11 PM -0800:
> Bill Landry wrote:
>> Erez Epstein wrote the following on 11/26/2006 1:24 AM -0800:
>>> Hello everybody,
>>>
>>>
>>> i have set up clamscan to scan all of the server using cron daily
>>> ( /usr/local/bin/clamscan -r -i --exclude-d
Bill Landry wrote:
Erez Epstein wrote the following on 11/26/2006 1:24 AM -0800:
Hello everybody,
i have set up clamscan to scan all of the server using cron daily
( /usr/local/bin/clamscan -r -i --exclude-dir=/sys --no-summary / )
the scan is taking too long conisdered to other virus scann
Erez Epstein wrote the following on 11/26/2006 1:24 AM -0800:
> Hello everybody,
>
>
> i have set up clamscan to scan all of the server using cron daily
> ( /usr/local/bin/clamscan -r -i --exclude-dir=/sys --no-summary / )
>
>
> the scan is taking too long conisdered to other virus scanners (about
Erez Epstein wrote:
and how can i shorten it while still scaning all files every night.
Don't scan all of them every night. There is no need to scan a file that
has not been modified since the last scan. There is probably no need to
scan your logs, /var, /usr, /opt, /proc, /dev, /bin, /sbin,
Here is a little script that will cover most of the bases.
Play around with it. I've only ever run it on my system so maybe it wont
work for you. Takes about an hour on my system to run "both".
#!/bin/sh
##
#
Hello everybody,
i have set up clamscan to scan all of the server using cron daily
( /usr/local/bin/clamscan -r -i --exclude-dir=/sys --no-summary / )
the scan is taking too long conisdered to other virus scanners (about 6 hours)
why does it taking so much?
and how can i shorten it while stil
13 matches
Mail list logo
