On Wed, Feb 21, 2018 at 08:48:44AM +0000, leloft wrote: > 1) the clamd.conf defaults installed automatically configure it > for systemd; and
I can't speak to a fresh install. However, after my dist-upgrade to Ascii the configuration was brought over without problems, and other than libsystemd0, I have no systemd components installed. So, while I don't know if the default clamd configuration configures it for systemd, I can tell you it is possible to configure it to run without most of systemd being installed. > 2) i want to change some of the default settings for more stringent > ones If the autoconfiguration doesn't let you change them, then you're back to configuring clamd by hand. > But following your advice and letting dpkg handle the intallation > automatically generates this clamd.conf: Ok, and what's wrong with it? > But when I try to dpkg-reconfigure clamd.conf (line2) > > #dpkg-reconfigure clamav-daemon > [ ok ] Stopping ClamAV daemon: clamd. > Configuring clamav-daemon > ------------------------- > > Some options must be configured for clamav-daemon. > > The ClamAV suite won't work if it isn't configured. If you do not > configure it automatically, you'll have to > configure /etc/clamav/clamd.conf manually or run 'dpkg-reconfigure > clamav-daemon' later. In any case, manual changes in [More] > > /etc/clamav/clamd.conf will be respected. > > Handle the configuration file automatically? [yes/no] no > > > Replacing config file /etc/clamav/clamd.conf with new version > Disabling old systemd service override options for clamav-daemon > Disabling old logrotate script for clamav-daemon > [FAIL] Clamav is not configured. ... failed! > [FAIL] Please edit /etc/clamav/clamd.conf and run > '/etc/init.d/clamav-daemon start' ... failed! invoke-rc.d: initscript > clamav-daemon, action "start" failed. > > # dpkg-reconfigure clamav-daemon > [FAIL] Clamav is not configured. ... failed! > [FAIL] Please edit /etc/clamav/clamd.conf and run > '/etc/init.d/clamav-daemon start' ... failed! invoke-rc.d: initscript > clamav-daemon, action "stop" failed. Right. You are telling dpkg to not configure clamd automatically. So, it marks it as unconfigured, and refuses to start it. You need to configure it by hand, and then start it up once you do that. This is my understanding of what is happening in the above output, but I could of course be wrong. > > # apt-get remove --purge clamav-daemon Reading package lists... Done > Building dependency tree > Reading state information... Done > The following package was automatically installed and is no longer > required: clamdscan > Use 'apt autoremove' to remove it. > The following packages will be REMOVED: > clamav-daemon* > 0 upgraded, 0 newly installed, 1 to remove and 5 not upgraded. > After this operation, 1,094 kB disk space will be freed. > Do you want to continue? [Y/n] y > (Reading database ... 147099 files and directories currently installed.) > Removing clamav-daemon (0.99.2+dfsg-6+deb9u1) ... > [FAIL] Clamav is not configured. ... failed! > [FAIL] Please edit /etc/clamav/clamd.conf and run > '/etc/init.d/clamav-daemon start' ... failed! invoke-rc.d: initscript > clamav-daemon, action "stop" failed. dpkg: error processing package > clamav-daemon (--remove): subprocess installed pre-removal script > returned error exit status 6 > Errors were encountered while processing: > clamav-daemon > E: Sub-process /usr/bin/dpkg returned an error code (1) > Ok, that should probably be reported as a bug. It should be possible to purge an unconfigured package, and the purge shouldn't fail because an already stopped service can't be stopped. > I can apt-get remove --purge clamav-daemon if I overwrite any > dpkg-reconfigured clamd.conf with the above systemd defaults. Again, what systemd defaults are you referring to? I haven't so far come across anything in any of the above output you provide which says it needs systemd. If you're talking about the dpkg output that says it's disabling old systemd overrides, then I don't see what that has to do with the configuration of clamav-daemon. > My concerns are therefore not so much about the clamd.conf file itself, > but more about the apparent systemd (pseudo-)dependency and the nature > of the systemd patch in ClamAV 0.99.2 (point 2 in OP) and above output > (line 2 after the dpkg-reconfigure 'no' command) > "Disabling old systemd service override options for clamav-daemon" > and by extension, whether the ClamAV package needs to be examined > for any cryptic systemd dependencies. I'm sure the clamav-daemon package will be devuanized eventually. If having that happen ASAP is important enough to you, then you may want to consider volunteering to devuanize it yourself. Greg -- web site: http://www.gregn.net gpg public key: http://www.gregn.net/pubkey.asc skype: gregn1 (authorization required, add me to your contacts list first) If we haven't been in touch before, e-mail me before adding me to your contacts. -- Free domains: http://www.eu.org/ or mail [email protected] _______________________________________________ Dng mailing list [email protected] https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
