On 29/01/2021 13:02, Reindl Harald wrote:
Am 29.01.21 um 13:55 schrieb lejeczek:
● user@0.service - User Manager for UID 0
Loaded: loaded
(/usr/lib/systemd/system/user@.service; static; vendor
preset: disabled)
Active: active (running) since Thu 2021-01-28
17:13:01 GMT; 2h 34min
On 28/01/2021 21:32, Lennart Poettering wrote:
On Do, 28.01.21 20:06, lejeczek (pelj...@yahoo.co.uk) wrote:
Hi guys
This absolutely boggled my mind, my brain exploded, but go easy on me as I
ain't an expert.
I have, meaning the "root" but other users too, _NO_ "~/.config/systemd" -
thus,
Am 29.01.21 um 16:27 schrieb lejeczek:
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
On Fr, 29.01.21 12:30, Ulrich Windl (ulrich.wi...@rz.uni-regensburg.de) wrote:
> Hi!
>
> I wonder whether this is a bug:
> When starting a socket unit that finds ist service active already, I get an
> error
> systemd[1]: libvirtd-tls.socket: Socket service libvirtd.service already
> active,
On Fr, 29.01.21 11:34, John Lane (syst...@jelmail.com) wrote:
> >
> > Is it possible you are playing some weird games with your machine ID
> > or boot ID?
> >
>
> Maybe. Yes. I have a oneshot service that writes /etc/machine-id using
> constant hardware-based info. But I've been using that for
For me it is pretty logical, as in: the service started in relation to
socket unit gets the respective socket.
If service is already started there is no way to pass additional socket
to it without restarting it.
It may even listen exactly on the socket specified, just creating it on
it's own.
W
Am 29.01.21 um 13:55 schrieb lejeczek:
● user@0.service - User Manager for UID 0
Loaded: loaded (/usr/lib/systemd/system/user@.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:
>
> Is it possible you are playing some weird games with your machine ID
> or boot ID?
>
Maybe. Yes. I have a oneshot service that writes /etc/machine-id using
constant hardware-based info. But I've been using that for over two
years without any issues.
I did notice this when trying to
Hi!
I wonder whether this is a bug:
When starting a socket unit that finds ist service active already, I get an
error
systemd[1]: libvirtd-tls.socket: Socket service libvirtd.service already
active, refusing.
systemd[1]: Failed to listen on Libvirt TLS IP socket.
When using systemd units in a
