On 4/20/2020 1:25 PM, Paul Kosinski via clamav-users wrote: > Andrew, > > Yeah, per your posting, I tried running 'configure' specifying > `--with-systemdsystemunitdir=no` and it seemed to be suppress the > systemd tie-in. (I didn't actually run 'make'.) > > It would be nice if this were documented somewhere. The "--help" info > from 'configure' only lists 'DIR' as an argument. The latest reference > to 'systemd' in NEWS.md is for version 0.99.2 (and the other ".md" > files have nothing), and I couldn't find anything about this new > approach in the documentation or faqs on GitHub. (Google doesn't turn > up anything definitive either.) > > In any case, the systemd tie-in is a *major* change: it turns ClamAV > from a mere package into a run-at-startup *service*, and needs to be > presented as such.
While I agree that it should be documented if it is installing systemd stuff, I don't think this is quite as bad as you think. After reading this thread, I took a look at my own system. I use ClamAV via avfilter for Courier, so I do not normally have the clamd daemon running. Since I recently updated to ClamAV 0.102.2, I was curious if anything had changed based on what you were seeing. I verified that the daemon is not running, but it did install a service file that is disabled by default. So unless you activate the service via systemd, it will not actually do anything. The freshclam daemon is running on my system, but that is intentional. According to systemd, freshclam is also disabled by default. It looks like this change would not cause any issues in your case unless you are actually using the systemd service to control the daemons. -- Bowie _______________________________________________ clamav-users mailing list clamav-users@lists.clamav.net https://lists.clamav.net/mailman/listinfo/clamav-users Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml
