> This appears to be inconsistent imho. > > Somehow I think systemd could be more clever here and scale down > RandomizedDelaySec= on boot depending on how far in the past the > timestamp of the stampfile is. > Say the last activation of the service was 12 hours ago, then scale > down RandomizedDelaySec=12h by dividing it by 12, so it would become > RandomizedDelaySec=1h. The further in the past, the shorter the delay > would become and the more likely that the timer fires eventually. > > And for consistencies sake, a (scaled) RandomizedDelaySec=1 should > also be reapplied on resume. >
That's right, if systemd would be capable of this behaviour, it would be very helpfull to not end up in a never updated system for example (like it might happen to my systems).
