[systemd-devel] Scheduling 3 periodic jobs using systemd

[Barry Scott]

> On 12 Jul 2024, at 09:50, t.schneider at disroot.org wrote:
> 
> There's no script (or whatsoever) in this backup functionality.
> It's only rsnapshot <https://wiki.archlinux.org/title/Rsnapshot> (https://wiki.archlinux.org/title/Rsnapshot) and systemd-timer <https://wiki.archlinux.org/title/Systemd/Timers> involved.
> 

You can change the ExecStart= to use flock, see man flock for details.

Off the top of my head something like:
ExecStart=flock --exclusive mylock rsnapshot

Add in full paths to make it robust.

Barry

> 
> Am 2024-07-12 10:35, schrieb Barry Scott:
> 
>> 
>> 
>>> On 12 Jul 2024, at 08:34, t.schneider at disroot.org wrote:
>>> 
>>> Setting the time of day requires detailed knowledge about the runtime of each job.
>>> 
>>> But this forecast is not accurate and this means any setting could result in same error.
>>> 
>> 
>> Agreed that is a problem with this approach.
>>  
>> Or you have the code that locks wait for the lock to be freed does that help?
>> Are you using flock in the script, then its a easy change.
>>  
>> You still cannot ensure the order, but you can ensure that they will all run sequentially.
>>  
>> Personally I encode the rules for my incremental vs. full backup into my hourly backups script.
>> So I only have one timer.
>>  
>> Barry
>>  

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/systemd-devel/attachments/20240712/e39059d2/attachment-0001.htm>