On Fri, 17 Jul 2020 01:46:06 +0200 Michael Biebl wrote: > Control: reassign -1 apt-listbugs > > Am 16.07.20 um 23:11 schrieb Francesco Poli: > > > [Unit] > > Description=Daily apt-listbugs preferences cleanup > > After=network.target network-online.target > > > > On the other hand, the original bug reporter (Oswald) sees that the > > service is triggered immediately after each wake-up from sleep. > > Before the network has had a chance to become available and working. > > Please see https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/ > > network-online.target is only relevant during boot, once the target has > been reached, it will stay up, it is not dynamic. > I.e. you can't use that to delay the execution of a service after > suspend-resume. > > If your service has such dynamic needs, this can't be expressed via > network-online.target and you should instead implement that in your > service directly. > > Reassigning accordingly.
Hello Michael, thanks for your prompt reply. OK, I acknowledge that the network-online.target check is not reliable enough, I was aware of that. But anyway, let's pretend the network check is completely absent. Why is the service triggered *immediately* during wake-up? It should wait at least 5 min (OnActiveSec=5min) or be triggered on the basis of the calendar scheduling (OnCalendar=*-*-* *:20) with a random delay (RandomizedDelaySec=20min). And it should *not* catch up with missed execution chances (since the timer is *not* a Persistent=true one). What am I missing here? -- 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
pgpX8TXb7mo3O.pgp
Description: PGP signature
