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