Hi Anders, On 06.05.2015 23:06, Anders Wegge Keller wrote: > I have experienced the same problem with systemd repeatedly trying to start > the daemon. Every ~300 μsec for about four hours makes for 71+ million lines > of syslog. > > As I see the problem, systemd does not consider the clamav-daemon service > as failed, when the preconditions are not met. Thus, it will repeatedly > attempt to start the service unit, when the socket is used.
I don't think that this is really the problem. The problem is that systemd does not slow down trying to restart the service as it does in other cases, e.g. if a service with Restart=always exits immediately. > To get around > this problem, I've moved[1] ConditionPathExistsGlob from the .service unit > to the .socket unit. By moving the check to the top of the chain, it appears > that systemd will not go into an endless loop, trying to fullfill the > requirements, that are un-fullfillable. I had considered something like that, but it has the bad side effect, that clamav-daemon will not be started upon installation. If the socket is started, clamav-daemon is started as soon as clamav-freshclam has downloaded the databases. So I hope that a newer version of systemd will eventually fix this problem. Best regards, Andreas _______________________________________________ Pkg-clamav-devel mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-clamav-devel
