Thanks for that clamav-daemon.socket.d/ hint. Up until now we've used debconf preseeding to configure the clamav- daemon package using the TCP* questions as part of package installation, but with this package upgrade it seems that mechanism is now obsolete... so we're trying to identify the best replacement approach (for the long term).
I looked at the Noble release notes, https://discourse.ubuntu.com/t/ubuntu-24-04-lts-noble-numbat-release- notes/39890#p-99950-clamav, (since Noble was released with ClamAV v1.4), but that section doesn't mention anything about changes to the way TCP sockets are configured.... Do we have the correct impression from the discussion in debbugs #1042377 that somewhere along the way to ClamAV v1.4, Debian's packaging was changed such that clamd.conf listening options are now ignored, but template and postinst code related to the TCP* debconf questions was not changed to reflect this fact? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2115847 Title: Jammy clamav-daemon no longer listening on TCP port after upgrade to 1.4.3+dfsg-0ubuntu0.22.04.1 (jammy-security) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/2115847/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
