Re: [clamav-users] ScanOnAccess issue when clamd launched from systemd
Mikko,
I suspected as much based on your description.
Use 'ps -efZ | grep clamd' to find out how the clamd process is running.
Check it when you run manually, and check it again when started by
systemd. I suspect yo
logs...
> Has anyone got ScanOnAccess working with SElinux enabled?
>
> Thanks
>
> Mikko
>
>
> From: Mikko Caldara
> Sent: 05 May 2016 16:47
> To: ClamAV users ML
> Subject: RE: [clamav-users] ScanOnAccess issue when clamd lau
From: Mikko Caldara
Sent: 05 May 2016 16:47
To: ClamAV users ML
Subject: RE: [clamav-users] ScanOnAccess issue when clamd launched from systemd
Hi Mickey,
I tried disabling SELinux and will report back later on that issue.
I understand OnAccess cannot prevent access or write attempts
if
of Mickey
Sola [ms...@sourcefire.com]
Sent: 05 May 2016 16:27
To: ClamAV users ML
Subject: Re: [clamav-users] ScanOnAccess issue when clamd launched from systemd
Mikko,
I know you didn't find anything in audit.log, but is your primary issue
resolved when you set SELinux to Permissive? Look
__
> From: clamav-users [clamav-users-boun...@lists.clamav.net] on behalf of
> Virgo Pärna [virgo.pa...@mail.ee]
> Sent: 05 May 2016 11:07
> To: clamav-users@lists.clamav.net
> Subject: Re: [clamav-users] ScanOnAccess issue when clamd launched from
> systemd
Pärna [virgo.pa...@mail.ee]
Sent: 05 May 2016 11:07
To: clamav-users@lists.clamav.net
Subject: Re: [clamav-users] ScanOnAccess issue when clamd launched from systemd
On Thu, 5 May 2016 09:50:03 +, Mikko Caldara
wrote:
> Not sure if it's related, but when I launch clamd *without* sys
On Thu, 5 May 2016 09:50:03 +, Mikko Caldara
wrote:
> Not sure if it's related, but when I launch clamd *without* systemd and then
> try to access an "infected" file, 2 problems occur:
>
> - clamd does not prevent access, despite having the option enabled
> - clamd goes into an infinite loop
kko.cald...@fca.org.uk]
Sent: 05 May 2016 09:34
To: ClamAV users ML
Subject: Re: [clamav-users] ScanOnAccess issue when clamd launched from systemd
SELinux is indeed enabled, but there's no blocking message in audit.log when
the error occurs.
After further retries, it seems the error
s...@hexadiam.com]
Sent: 04 May 2016 19:11
To: ClamAV users ML
Subject: Re: [clamav-users] ScanOnAccess issue when clamd launched from systemd
Is SELinux enabled on that system? If so, I would look to see if SELinux
is blocking.
On 05/04/2016 09:29 AM, Mikko Caldara wrote:
> Hello,
>
Is SELinux enabled on that system? If so, I would look to see if SELinux
is blocking.
On 05/04/2016 09:29 AM, Mikko Caldara wrote:
Hello,
I'm trying to configure OnAccess scanning on the whole drive, as read in this
post blog:
http://blog.clamav.net/2016/03/configuring-on-access-scanning-in-c
Hello,
I'm trying to configure OnAccess scanning on the whole drive, as read in this
post blog:
http://blog.clamav.net/2016/03/configuring-on-access-scanning-in-clamav.html
(first example)
It works fine if I launch clamd manually, with: /usr/sbin/clamd -c
/etc/clamd.conf &
If I use systemd to l
On Fri, 2014-01-31 at 15:01 +0100, Pieter Caron wrote:
> On 29.01.2014 16:24, Greg Folkert wrote:
>
> >
> > You specifically *INCLUDE* /home/pc... you cannot Exclude a part of it
> > once you Include it. The Include Trumps the Exclude in this instance. At
> > least that is what I'm seeing myse
On 29.01.2014 16:24, Greg Folkert wrote:
>
> You specifically *INCLUDE* /home/pc... you cannot Exclude a part of it
> once you Include it. The Include Trumps the Exclude in this instance. At
> least that is what I'm seeing myself.
>
> I haven't tried changing the order of the rules yet and probab
On Wed, 2014-01-29 at 15:57 +0100, Pieter Caron wrote:
> Dear all
>
> I have installed clamav 0.98.1 on Linux version 3.12.9-1-ARCH x86_64
>
> Clamscan and Clamdscan are working perfectly, also the update via
> Freshclam is ok.
>
> However I have a problem with ScanOnAccess:
>
> Using the foll
Dear all
I have installed clamav 0.98.1 on Linux version 3.12.9-1-ARCH x86_64
Clamscan and Clamdscan are working perfectly, also the update via
Freshclam is ok.
However I have a problem with ScanOnAccess:
Using the following clamd.conf file:
LogFile /var/log/clamav/clamd.log
LogTime yes
Pid
15 matches
Mail list logo
