Mailinglist Archive: opensuse-factory (807 mails)

< Previous Next >
Re: [opensuse-factory] why is tumbleweed still using cron?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 2017-02-28 19:43, Ruediger Meier wrote:
On Tuesday 28 February 2017, Andrei Borzenkov wrote:
28.02.2017 20:57, Carlos E. R. пишет:
On 2017-02-28 18:12, Andrei Borzenkov wrote:
28.02.2017 19:44, Stefan Seyfried пишет:
On 28.02.2017 11:58, Simon Lees wrote:
So the executive summary about systemd timers is: *
not started if the user is not logged in or does not
use GNOME

This part is not entirely true, KDE, Enlightenment and
possibly others

Doesn't matter. If you are not logged in, your timers will
not run.

Which is not entirely correct. But I suppose you are not
interested and do not care anyway :)

Others may ;-)

I already answered this in this thread.


Even on default systemd setup a user can easily start his systemd
user instance using a cronjob:

@reboot sleep 9999d &

... 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


The user instance will run as long as the sleep command is running.
Thanks cron's superior design this sleep will also survive crond
restarts/stops etc. :)

Wow. Looks... er... kludgy ;-)


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


- --
Cheers / Saludos,

Carlos E. R.

(from 42.2 x86_64 "Malachite" (Minas Tirith))
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iF4EAREIAAYFAli1x78ACgkQja8UbcUWM1xW2gD/cMXrnuIy2j4nkNzLJmC/wf3D
x1Nz+SJPU0ZJJftJfmUA/0PiqKBDIo9hYEbYUgiU0n9LRutyDu2yipUUa+HlzBHC
=kVK3
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-factory+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups