On Sun, 26 Jul 2020 22:06:23 +0200 Michael Biebl wrote: > Am 26.07.20 um 21:36 schrieb Francesco Poli: [...] > > Dear Michael, > > I am still convinced that this is a bug in systemd, as explained above. > > I am reassigning back the bug report to package systemd. > > > > If you think that the timer unit can be modified so that it behaves as > > intended, please tell me how I should modify it. > > Just to recap the intended behavior: the timer should trigger the > > corresponding oneshot service 5 min after the timer activation and then > > hourly, with a random delay between 0 and 20 min, *without* catching up > > with missed execution chances, and it should *not* trigger the service > > immediately during a wake-up from sleep. > > Maybe this is a misunderstanding.
It's possible. And it may well be on my side. Let's try and clarify... > Persistent=true is relevant when you > reboot/power down a system. In your case, the system is suspended and > woken up again. Exactly! So why does it trigger *immediately* during wake-up? Was the timer inactive during sleep and then re-activated during wake-up? If this is the case, then it should wait at least 5 min (OnActiveSec=5min) or trigger on the basis of the calendar scheduling (OnCalendar=*-*-* *:20) with a random delay (RandomizedDelaySec=20min). Was the timer still considered active during sleep? If this is the case, then the OnActiveSec=5min trigger should not happen at all during wake-up and the timer should just trigger on the basis of the calendar scheduling (OnCalendar=*-*-* *:20) with a random delay (RandomizedDelaySec=20min). Yet, the timer triggers during each wake-up, without waiting. This is why I think the bug is in systemd. -- http://www.inventati.org/frx/ There's not a second to spare! To the laboratory! ..................................................... Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE
pgpNAZsGJf6YT.pgp
Description: PGP signature