[systemd-devel] Persistent timers delay Type=idle units

[Andrey Borzenkov]

В Wed, 23 Apr 2014 05:57:39 +0200
Lennart Poettering <lennart at poettering.net> пишет:

> 
> Ah, OK, I think I got it now:
> 
> You have services that are to be started by timers that take a long time
> to complete. THe timers have been configured to be persistent. If the
> system comes up and the timestamp files suggest that the timers need to
> be triggered immediately this is done, adding the service execution time
> to the bootup time. This is normally not a problem except when there's
> some other bootup service that uses Type=idle which will then be
> affected by these long running services...
> 
> Did I get this right?
> 
> Hmm, this sounds nasty. I wodner what we can do about it...
> 

Provide "boot completed" indication?

systemd already provides "starting" and "running" states. Which
logically implies that bootup is finished when "starting" is
replaced by "running".

Add new timer condition which fires at this point? This will stop
misusing Idle for poor man's replacement of proper "boot completed"
event.