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

[Leonid Isaev]

Hi,

On Wed, 23 Apr 2014 05:57:39 +0200
Lennart Poettering <lennart at poettering.net> wrote:

> [...]
> 
> 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?

Yes. Of course, the meaning of "long" really depends... but it can be ~10 sec.

> 
> Hmm, this sounds nasty. I wodner what we can do about it...
> 
> Maybe we should add a new setting PersistentExtraSec= to timer units or
> so which allows delaying these kind of timers by an extra margin. Would
> this work for you?

Yes, I think so. Actually, that's what Thomas proposed on arch-general...

> 
> > > > What does "systemctl list-jobs" print when this happens? (i.e. when the
> > > > bootup is supposedly delayed?)
> > 
> > I'll have to test this, but I'll speculate that list-jobs will show nothing
> > by the time I login, because it takes about 30 sec for me to enter login
> > credentials... 
> 
> Use "systemctl enable debug-shell"...

OK will do. I didn't know about the debug shell.

Thanks,
L.

-- 
Leonid Isaev
GPG fingerprints: DA92 034D B4A8 EC51 7EA6  20DF 9291 EE8A 043C B8C4
                  C0DF 20D0 C075 C3F1 E1BE  775A A7AE F6CB 164B 5A6D
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.freedesktop.org/archives/systemd-devel/attachments/20140423/9959d3fe/attachment.sig>