Mandi! Marco Gaiarin
In chel di` si favelave...
> > as it is a pattern, not a path, might work ;-)
> Ok, works. But as i've stated yesterday, if some user create a
> ``quarantena'' folder somewhere, that folder are not scanned. This is
> not so good...
> There's some way that i can match an exac
Mandi! Bob Hutchinson
In chel di` si favelave...
> try
> --exclude-dir=quarantena
> as it is a pattern, not a path, might work ;-)
Ok, works. But as i've stated yesterday, if some user create a
``quarantena'' folder somewhere, that folder are not scanned. This is
not so good...
There's some way
Mandi! Bob Hutchinson
In chel di` si favelave...
> --exclude-dir=quarantena
> as it is a pattern, not a path, might work ;-)
Ok i'll try. But in this way some user can fake the scan simply putting
a file in a ``quarantena'' folder...
There's some way i can put an exact path? / is a special cha
On Monday 06 Feb 2006 14:04, Marco Gaiarin wrote:
> I'm tring to build up some sort of ``system scan'' script that,
> nightly, scan all my debian/samba servers and report infections.
>
> Script works, but i've some strange result, or at least probably i've
> not understood well the clamscan command
I'm tring to build up some sort of ``system scan'' script that,
nightly, scan all my debian/samba servers and report infections.
Script works, but i've some strange result, or at least probably i've
not understood well the clamscan command line options.
I start clamscan with a cmdline like:
