Re: systemd+anacron breaks cron jobs
- Date: Wed, 05 Dec 2018 10:04:23 +0100
- From: kjonca@xxxxxxxxxxxxxx (Kamil Jońca)
- Subject: Re: systemd+anacron breaks cron jobs
Michael Biebl <biebl@xxxxxxxxxx> writes:
> Am 05.12.18 um 08:54 schrieb Kamil Jońca:
>> "User" task aren't started until user logs in. (You should play with
> I haven't read the full discussion, so I missed the part that you are
> apparently using a user crontab.
To clarify things:
1. In original post I described system task which CAN (and sooner or
later will) be migrated to systemd timers.
But then You said that:
2. anacron can be dropped - which in general is not true, because
systemd cannot provided proper functionality for user units.
> It's correct, that "systemd --user" is started if you log in, or if you
> explicitly enable linger for this user (then it is started during boot).
>> which in turn, can break ALL your "user" units)
> I'd be interested to know, what exactly you have in mind here. I'm not
> aware of such a breakage.
For example: I have (--user)
kj-keepassx.service - my own service with keepasx
xscreensaver-monitor.service - my own service which to monitor screensaver
These services should NOT be run withoud graphical login.
But I would run my user timers. How to achieve this?
with cron/anacron I simply put line in my (ana)crontab.
Classical music is the kind we keep thinking will turn into a tune.
-- Kin Hubbard, "Abe Martin's Sayings"