FWIW, I had to implement a monthly/weekly/daily backup scheme a while
back and determined that the most reliable way to do it was to handle
it myself rather than trying to encode it all through systemd units.
The script does this basically:
#!/usr/bin/env python3
from datetime import datetime
no
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
> On 15 Jul 2024, at 13:59, Nils Kattenbeck 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 Afte
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
On Mon, Jul 15, 2024, 14:52 wrote:
> Actually there's no dedicated *.service file for ea
On Di, 09.07.24 18:02, Laurent GUERBY (laur...@guerby.net) wrote:
> Hi,
>
> On a debian testing system (systemd 256.2-1) I created a user with:
>
> trixie# homectl create utest --storage=luks --ssh-authorized-keys="xxx"
>
> The I used ssh to login as the user
>
> ssh utest@trixie
>
> And it all wo
