On Mon, Sep 25, 2023 at 08:58:08PM +0200, Andrea Bolognani wrote:
For most services, the socket paths can be derived trivially from the name of the daemon: for virtqemud, for example, they will be
/run/libvirt/virtqemud-sock /run/libvirt/virtqemud-sock-ro /run/libvirt/virtqemud-admin-sock
libvirtd and virtproxyd are the exceptions, since their socket paths will be
/run/libvirt/libvirt-sock /run/libvirt/libvirt-sock-ro /run/libvirt/libvirt-admin-sock
So we still need to be able to provide a custom @sockprefix@ in those cases, but in the most common scenario we can do away with the requirement by introducing a sensible default.
Signed-off-by: Andrea Bolognani <abologna@redhat.com> --- src/meson.build | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com> With regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|