Web lists-archives.com

Re: systemd+anacron breaks cron jobs




Michael Biebl <biebl@xxxxxxxxxx> writes:

> Am 05.12.18 um 10:04 schrieb Kamil Jońca:
>> Michael Biebl <biebl@xxxxxxxxxx> writes:
>
>>>>  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.
>
> If those services are tied to a X login session, they should not be
> started via systemd --user (at least, not yet)
>
> Let me go into a bit more detail.
>
>
> There is only ever *one* systemd --user instance per user. It is
> typically started, the first time you log in and stopped, once there is
> no more active login session for a particular user.
>
[...snip...]
I knew all you wrote.
So I my question still is:

How can I:
1. start services only with graphical login and
2. start timers irrespective of graphical login.
KJ



-- 
http://stopstopnop.pl/stop_stopnop.pl_o_nas.html
It's a .88 magnum -- it goes through schools.
		-- Danny Vermin