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 clamav 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
