I am using EPEL version and I don't think I have a choice. But it _might_ 
be worth looking at difference.

Thanks in advance,
-Neel.

From: Andrew C Aitchison <and...@aitchison.me.uk>
Sent: Mon, 10 Jun 2024 16:42:49
To: neel roy via clamav-users <clamav-users@lists.clamav.net>
Cc: neel roy <neelsm...@rediffmail.com>, Matus UHLAR - fantomas 
<uh...@fantomas.sk>
Subject: Re: [clamav-users] Using clamd@ service vs launching clamd from 
command line

On Mon, 10 Jun 2024, neel  roy via clamav-users wrote:

> Thanks.
>
> On selinux, which is the case with me, running clamd as *standalone
> process* is more advantageous than running as systemd service. The
> reason is mentioned in the post by someone else couple of years
> back. I am facing similar
> issue: https://github.com/Cisco-Talos/clamav/issues/582
>
> In case of systemd process, clamd can have graceful exit using
> "systemd stop clamd@scan" but same can be achieved by
> "kill -TERM <pid of clamd>" if clamd is 
running as
> standalone executable.
>
> So given a choice, what would be reason why a user would want to run
> clamd@ service (instead of standalone process)?

Are you using clsmav from the clamav site, or the EPEL version ?

SystemD and permission settings may be different in the two packaged
versions.

I know that that the .deb from clamav is sufficiently different from
the version that ships with Ubuntu that I stick with the Ubuntu version,
even though it is not as up-to-date.

--
Andrew C. Aitchison                 
     Kendal, UK
                  
 and...@aitchison.me.uk
_______________________________________________

Manage your clamav-users mailing list subscription / unsubscribe:
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/Cisco-Talos/clamav-documentation

https://docs.clamav.net/#mailing-lists-and-chat

Reply via email to