Thanks Eero for the verification of the fix I added (starting freshclam again which was a regression. You are right that clamav-daemon doesn't start for the reasons I outlined before of the condition being not met initially and not picked up later by systemd.
I'm not sure about a sleep-loop to fix this up but I really appreciate dropping the info for anyone who wants this. I'd expect a proper solution would be something where systemd is realizing that the condition is "now true" and starts it then. Since that part is not a regression we should discuss and agree with Debian in how to do so. I started the discussion before on the linked Debian bug, but regarding clamav-daemon not starting the response was "this is okay." Would you mind opening a bug there or chiming in on the linked bug again to push your argument - I also already added several suggestions there how to start it, but they need some improvement for this "realizing later" that the condition is met. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1590688 Title: clamav-daemon doesn't start after installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1590688/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
