Web lists-archives.com

Re: systemd+anacron breaks cron jobs




Am 05.12.18 um 10:47 schrieb Kamil Jońca:
> 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

You can't. At least not yet. Use ~/.config/autostart
This is what I trying to explain.

> 2. start timers irrespective of graphical login.

If you want them to be started during boot, use enable-linger


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

Attachment: signature.asc
Description: OpenPGP digital signature