generation of virtproxd socket files

Jim Fehlig jfehlig at suse.com
Mon Feb 8 23:09:16 UTC 2021


Hi All,

I received a report [1] and verified that virtproxyd*.socket files have broken 
syntax. E.g. from virtproxyd.socket

[Unit]
Description=Libvirt proxy local socket
Before=virtproxyd.service
libvirtd.socket libvirtd-ro.socket libvirtd-admin.socket libvirtd-tcp.socket 
libvirtd-tls.socket

virtproxyd.socket should 'Conflicts' with the libvirtd sockets. I suspect this 
regressed in the switch to meson. I checked a libvirt 6.0.0 installation and 
indeed it has

Conflicts=libvirtd.socket libvirtd-ro.socket libvirtd-admin.socket 
libvirtd-tcp.socket libvirtd-tls.socket

I blame it on Monday and my mind stuck in the weekend, but I spent too much time 
trying to figure out how those socket files are generated before writing this 
mail. It would be much appreciated if someone can give me a nudge in the right 
direction :-).

Regards,
Jim

[1] https://bugzilla.opensuse.org/show_bug.cgi?id=1181838




More information about the libvir-list mailing list