If you're using systemd timers, you get this behavior for free because those timers only activate service units. If the service is already active, nothing happe

If you're using systemd timers, you get this behavior for free because those timers only activate service units. If the service is already active, nothing happens. (Of course, this can be surprising in a different way when you expect a new job to start, but it does not because a previous one is still lingering. Not saying it's better or worse, just pointing out for those who don't know.)