AFAIK they are independent and are taken into account when either a) both units are started simultaneously (e.g. they have a Wants= dependency) or b) one unit is already starting while the other unit is activated. Then the activating unit should still wait for the currently activating unit. Though it has been a while since I toyed around with that. I am unsure if timer units which elapse at the same time qualify for a) (they might, since systemd tries to combine close timers into one system wakeup at least) but they should definitely qualify for b) if you start one time shortly after the other.
On Mon, Jul 15, 2024, 18:22 Barry <barry@xxxxxxxxxxxxxxxx> wrote:
> On 15 Jul 2024, at 13:59, Nils Kattenbeck <nilskemail@xxxxxxxxx> wrote:
>
> It might make more sense to create three services. Otherwise you can add overrides for some of them (e.g. /etc/.../rsnapshot@weekly.service) with only a [Unit] section containing a Before=/After= declaration
Are you sure using After= will have any effect for services started from timer units?
I have assumed that services started via timers do not use the ordering directives.
But I am very unsure what would happen, and I am not never a system to experiment at the moment.
Barry
