On Tue, Jun 15, 2021 at 7:19 PM G.W. Haywood via clamav-users <
clamav-users@lists.clamav.net> wrote:
> Hi there,
>
> On Tue, 15 Jun 2021, Lee, Raymond via clamav-users wrote:
>
> > ... I don't want this thread to become a debate about whether or not to
> > scan the entire system. I was just look
Hi there,
On Tue, 15 Jun 2021, Lee, Raymond via clamav-users wrote:
... I don't want this thread to become a debate about whether or not to
scan the entire system. I was just looking for insight into my question
about clamd and SELinux.
Sure, with you. FWIW I don't scan Linux systems. Prim
On Mon, Jun 14, 2021 at 6:50 PM G.W. Haywood via clamav-users <
clamav-users@lists.clamav.net> wrote:
> Hi there,
>
> On Mon, 14 Jun 2021, Lee, Raymond via clamav-users wrote:
>
> > I've been having trouble with using clamdscan to scan my entire system
> ...
>
> Then don't do it!
> There are lot
Hi there,
On Mon, 14 Jun 2021, Lee, Raymond via clamav-users wrote:
I've been having trouble with using clamdscan to scan my entire system ...
Then don't do it!
There are lots of things in Unix-like filesystems (and Linux is a kind
of Unix) which should not be scanned with ClamAV.
Unix expo
Hi all,
I've been having trouble with using clamdscan to scan my entire system (
'clamdscan --multiscan --fdpass /' ) when SELinux is in Enforcing mode due
to files of certain SELinux context types.
Environment:
- CentOS 7 with the following packages from the yum repo:
clamav-lib-0.103.2-1.el7.x
Folks,
In my mail.log file, everything runs fine then
all of a sudden I have been seeing “Requeuing: Maximum time exceeded.
Something cannot handle this message. at /var/qmail/bin/qmail-scanner-queue.pl
line 529.” I have to shutdown clamd (kill -9 usually, it never dies
dow
