Re: Antw: [EXT] Re: Still confused with socket activation

[Andrei Borzenkov <arvidjaar@xxxxxxxxx>]

On Tue, Feb 9, 2021 at 11:54 AM Ulrich Windl
<Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx> wrote:
>
> Thanks and "back to the mess": If I use libvirtd.service instead of
> libvirtd-tls.socket, it does *not* open the TLS socket, even though the
> configuration file contains "listen_tls=1"...

libvirtd --listen

Did you read the link I gave you on the pacemaker list?

https://bugzilla.redhat.com/show_bug.cgi?id=1750340#c0

quoting

--><--
Thus if the mgmt app / admin wants to use TCP/TLS sockets they have two choices

  - To continue the old approach (setting --listen in
/etc/sysconfig/libvirtd), then they MUST use 'systemctl mask ...' for
all the socket units listed above, before libvirtd.service is started.
--><--

Does it not work?
_______________________________________________
systemd-devel mailing list
systemd-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/systemd-devel