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

["Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>]

>>> Andrei Borzenkov <arvidjaar@xxxxxxxxx> schrieb am 09.02.2021 um 10:14 in
Nachricht
<CAA91j0UtJmQ0y3dGLA6E0xiWXG_UXavY85bKyTYqk5_k+F8Gzg@xxxxxxxxxxxxxx>:
> 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?

The point is that masking is still required ("nail down system with silver nails once you killed it, just to make sure it doesn't resurrect") as "disabling" the sockets is not enough.
Now it works.

Regards,
Ulrich






_______________________________________________
systemd-devel mailing list
systemd-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/systemd-devel