Bug#913303: systemd: RandomizedDelaySec should inherit the clock of the timer that triggered it

[Michael Biebl]

Am 09.11.18 um 11:49 schrieb Lars Luthman:

> When the computer is suspended, the randomized delay keeps on running instead
> of pausing, and when it's woken up, the timer is 7 minutes nearer to expiring
> rather than 0 minutes as expected. If the delay expires while the computer is
> suspended, systemd will immediately run the job on wakeup rather than waiting
> 7 more minutes. If the delays for several timers expire before the wakeup, all
> those jobs will run at once, which is what RandomizedDelaySec is meant to
> avoid.
> 
> I would expect RandomizedDelaySec to add a random delay _using the same clock
> as the timer that triggered it_, in this case OnUnitInactiveSec. That would
> cause a more expected behaviour.

This would be a significant change in behaviour. As such, this should be
raised upstream and not handled as a downstream bug report.

Could you please file an issue at
https://github.com/systemd/systemd/issues

Thanks,
Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20181111/15a13e0f/attachment-0002.sig>