On 10.06.24 10:29, neel roy via clamav-users wrote:
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)?
I guess this is only issue related to selinux.
clamd as a systemd "service" is the same daemon as standalone process, it's
just different selinux policy applied
You would only want clamd as standalone process when you want selinux but
don't want to configure it.
--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Enter any 12-digit prime number to continue.
_______________________________________________
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
