[systemd-devel] service runs - but it's not really there

[Reindl Harald]

Am 29.01.21 um 13:55 schrieb lejeczek:
>>> ● user at 0.service - User Manager for UID 0
>>>     Loaded: loaded (/usr/lib/systemd/system/user at .service; static; 
>>> vendor
>>> preset: disabled)
>>>     Active: active (running) since Thu 2021-01-28 17:13:01 GMT; 2h 
>>> 34min ago
>>>   Main PID: 854314 (systemd)
>>>     Status: "Startup finished in 44ms."
>>>      Tasks: 35
>>>     Memory: 69.3M
>>>     CGroup: /user.slice/user-0.slice/user at 0.service
>>>             ├─init.scope
>>>             │ ├─854314 /usr/lib/systemd/systemd --user
>>>             │ └─854319 (sd-pam)
>>>             └─syncthing.service
>>>
>>> exists and gets auto started by "systemd" without any asking really.
>>> This is really very bad, no?
>>> What am I missing here?
>> systemd at the very least will spawn your per-user dbus daemon, which
>> is needs to be available for many programs to function. Even others
>> require systemd themselves.
>>
>> Lennart
>>
>> -- 
>> Lennart Poettering, Berlin
> I think I found it, in my opinion a very cheeky bastard - syncthing - 
> who does this:
> 
> [Install]
> WantedBy=default.target
> 
> which results in:
> 
> -> $ llr /etc/systemd/user/default.target.wants/
> total 0
> lrwxrwxrwx. 1 root root 39 Jan 26 10:39 syncthing.service -> 
> /usr/lib/systemd/user/syncthing.service
> 
> So those of you on RHEL and derivatives (I assume that same rpm goes to 
> all those) - suffices to install "syncthing" an you have your "roor" 
> does as above and if you are not aware then the "root" does that with 
> you not even knowing.
> 
> As a matter of sharing opinions - is that a good & healthy practice to 
> make & distribute packages like that?

what is your problem?

it's an ordinary user session and not some mystery of "root does as above"

RTFM https://www.freedesktop.org/software/systemd/man/user@.service.html 
instead talking about "very cheeky bastard - syncthin"