Mailinglist Archive: opensuse-factory (807 mails)

< Previous Next >
Re: [opensuse-factory] why is tumbleweed still using cron?
On Tuesday 28 February 2017, Andrei Borzenkov wrote:
28.02.2017 21:55, Carlos E. R. пишет:
...

... no lingereing settings by user root are needed.

$ ps aux | grep rudi rudi 28099 0.0 0.0 36052 4004 ? Ss
19:34 0:00 /usr/lib/systemd/systemd --user rudi 28101 0.0
0.0 62152 2184 ? S 19:34 0:00 (sd-pam) rudi 28102
0.0 0.0 0 0 ? Zs 19:34 0:00 [sh] <defunct> rudi
28103 0.0 0.0 4248 660 ? S 19:34 0:00 sleep 9999d

...

Then, the user timers run because there is at least one process of
that user.

No. Because there is systemd user instance for this user.

There are 3 cases:

1. Per default there is only a systemd user instance if "logged in".
2. Adminstrators may disable user instances completely.
3. Administrators may enablelingereing to always have user instances.

regarding 1: It's very confusing ... what does it mean "logged in"?. A
cron job would start a user instance but login via "su" would not.
Moreover I've seen systems where the user instances where not killed on
logout.

regarding 3: It's very unlikely because it does not even seem possible
to enable lingering for ALL users and probably no adminstrator would
run hundreds or thousands of processes (one per user).


Alltogether for me it looks like systemd timers are not a good choice
for users who want to schedule jobs reliable depending on calendar
schedules. A user would require much administrator knowledge just to be
able to find out when his jobs would run and when not.


cu,
Rudi
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-factory+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups