On 2023-05-07 20:37, Per Jessen wrote:
Carlos E. R. wrote:
On 2023-05-07 18:26, Per Jessen wrote:
Andrei Borzenkov wrote:
On 07.05.2023 18:58, Per Jessen wrote:
Side question - how do I make a user timer run when the user is not logged in?
If you enable lingering for a user, systemd user instance is started on boot (instead of first time user logs in). You will need configure your unit to be auto-started.
Note that it will start everything. There is no way to start one single unit. I am not sure if it is possible to distinguish between start due to lingering or start due to use logon. It depends on what is started by various desktop environments.
I think that is all okay - I am only looking to emulate the crontab behaviour as closely as possible. For the user, there are two key things - running a job regularly (most often daily) and on reboot. (the @reboot crontab entry).
Huh... what's wrong with using crontab instead? Less work.
One key thing is that crontab keeps its user tabs in the /var filesystem.
Ok. Didn't think of that, because when I do a backup I take it all. Mail is also in var. Databases. I prefer jobs under /etc/cron*, too.
That is annoying and means extra work when doing backups. Second, same reason why we are moving toward systemd timers on the system side.
I'm not moving towards systemd timers, I do not see the advantage... -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)