On Sun, 26 Jul 2020 22:22:55 +0200 Michael Biebl wrote: [...] > Afaics, the problem is, that your service does not properly handle the > case, when the network is not available.
It does, that's the reason why the operation is attempted hourly. > Even if systemd would delay timer events after a resume: How long should > it wait? 30s, 1min? How would that robustly solve your problem? How > would that guarantee that after 1min network is available? It should wait at least 5 min (as specified in OnActiveSec=5min), because we are almost sure that immediately during wake-up is too early. Hence, attempting the operation during wake-up is a bad idea. If 5 min after wake-up is still too early to have a working network, no big deal, the service will try again hourly... -- 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
pgpHRlr8bo_wL.pgp
Description: PGP signature
