Hi there,
On Wed, 30 Sep 2020, Dave Sill via clamav-users wrote:
"G.W. Haywood via clamav-users" wrote:
There are ways around that, even if you don't want to run clamdscan
(and clamd) as root - which I'd entirely understand.
Is --fdpass one of them? And --stream? Any others?
No. I'd be
"G.W. Haywood via clamav-users" wrote:
>
> There are ways around that, even if you don't want to run clamdscan
> (and clamd) as root - which I'd entirely understand.
Is --fdpass one of them? And --stream? Any others?
> >We've got about 3000 Linux systems that we'd like to periodically scan,
> >
Andrew C Aitchison via clamav-users wrote:
>
> No. clamD scans data passed to it by clamdscan, usually over a socket or
> pipe.
Ah... I missed INSTREAM in the clamd man page. Locally, though, surely
SCAN/CONTSCAN/etc, are nuch more efficient. And remotely, sending the
entire contents of the syst
On Wed, 30 Sep 2020, Dave Sill via clamav-users wrote:
"G.W. Haywood via clamav-users" wrote:
In the second scan, how did clamscan manage to do what it claims to
have done in the time that it did it?
OK, you could have just said that the cache is internal to each invocation
of clamscan, b
Hi there,
On Wed, 30 Sep 2020, Dave Sill via clamav-users wrote:
The clamscan man page says:
--disable-cache
Disable caching and cache checks for hash sums of scanned files.
I've looked high and low via google, strace, looking at source code, conducting
tests,
and I see no
The clamscan man page says:
--disable-cache
Disable caching and cache checks for hash sums of scanned files.
I've looked high and low via google, strace, looking at source code, conducting
tests,
and I see no sign of caching done by clamscan. Is this on the to-do list?
We'd
