On 2023-08-13 17:42:29 [+0200], Andreas Guenther wrote: > you can clearly see that the service is triggered by the associated > socket! This was not the case with Debian Linux Bullseye! > > The only currently working solution is this: > > systemctl disable --now clamav-daemon.socket > systemctl enable --now clamav-daemon.service > > For only one system upgrade, that's pretty sloppy. Why do I need the > socket here if it runs better without it?
There went something wrong with the dependency of the socket vs service file. I just fixed that. The intention was to start the service via the socket file in case it was not yet running. Usually because the database files (after a fresh install) are missing. Sebastian
