Processed: Re: [Pkg-clamav-devel] Bug#775112: systemd: repeatedly tries to start clamav

[Andreas Cadhalpun]

Hi Michael,

On 15.01.2015 23:01, Michael Biebl wrote:
> Am 15.01.2015 um 22:18 schrieb Debian Bug Tracking System:
>> Changed Bug title to 'systemd: don't start services every few ms if condition fails'
>
> Systemd does throttle start attempts. See man systemd: StartLimitInterval=

Systemd does not throttle start attempts in the following case:
  * The socket is active and receives traffic.
  * The service can't be started, because a condition fails.

Systemd just tries to start the service every few milliseconds (using 
one CPU core) until the socket is stopped.

This can be easily reproduced with clamav-daemon.{service,socket} if no 
databases are present in /var/lib/clamav.

>> Changed Bug title to 'systemd: log if a condition prevents starting a unit'
>
> Systemd does keep state of failed conditions.
> If you inspect the service state, it will look like:

Yes, but the journal/syslog does not contain this information, only:
systemd[1]: Started Clam AntiVirus userspace daemon.
systemd[1]: Started Clam AntiVirus userspace daemon.

There should be something like:
"systemd[1]: Condition failed for Clam AntiVirus userspace daemon."

>  From my POV, the two bugs you filed are already adressed in systemd.
> Please eloborate.

I hope it's clear now, where I see these two bugs.

Best regards,
Andreas