Am 26.07.20 um 22:06 schrieb Michael Biebl: >> 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.
Afaics, the problem is, that your service does not properly handle the case, when the network is not available. 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?
signature.asc
Description: OpenPGP digital signature
