I try to create a timer unit for weekly and daily backups. For example with the weekly unit, it should be executed once in a week, some minutes after login. If the unit was successful, it should shutdown and not start again until the next week. If a start of this unit was missing, it should be start again some minutes after the next login.
But for some unknown reason, the current unit starts after every login when I reboot the laptop. I am relatively sure that this timer unit is set up wrong, but unfortunately I don’t know how I can implement such a unit better with the functions mentioned above.
[Unit]
Description=Run backup weekly
Requires=backup.service
[Timer]
Unit=backup.service
OnCalendar=weekly
RandomizedDelaySec=120
Persistent=true
[Install]
WantedBy=timers.target
the timer has no idea if it was triggered during last boot. It only has the context of “this” boot, so it will do it right after a reboot and set a timer to start the service again after a week of uptime.
So if you reboot every day, it will trigger the service every day, even though you set it to weekly in the timer.
So it’s up to your .service file to determine if it has been run this week or not.
the timer has no idea if it was triggered during last boot. It only has the context of “this” boot, so it will do it right after a reboot and set a timer to start the service again after a week of uptime.
This is not correct.
Persistent=truesaves the last time the timer was run on disk. From thesystemd.timerman page:Takes a boolean argument. If true, the time when the service unit was last triggered is stored on disk. When the timer is activated, the service unit is triggered immediately if it would have been triggered at least once during the time when the timer was inactive.
OP needs to remove
Requires=backup.servicefrom the[]section so it stops running it when it start the timer on boot.This is the correct answer.
You have the timer requiring backup.service, so it will run that service every time the timer starts on boot. Remove
Requires=backup.service, and that will fix the issue.OK, many thx for the tips. Since my script in the service file is already doing some logging, i will try to use the last log entry, to find out, when it was last time running and exit the script, if it is not in the timeframe of 1 week.
Your systemd file looks ok, but I think it’s doing exactly what you are telling it.
The solution may lie in the backup.service. Is that code you can modify? The OnCalendar=weekly doesn’t specify when in the week the service should run so that config may be vague.
If I understand the desired function here, you will need the service up all the time. It will just wait politely and occasionally run the specific backup script. It’s up to the backup script to determine when the last backup was made and either exit early because it hasn’t been a week or run the backup and reset a flag file.
At least that’s the approach I would take. Systemd is a very vigilant, but very stupid, service manager. It just watches and triggers services based on just a few criteria. Any logic more complex needs to go in the service itself.
