On 03/07/2013 12:37 PM, Saravanan Shanmugham (sarvi) wrote: > > Just changing > # define LIBVIRTD_PRIV_UNIX_SOCKET LOCALSTATEDIR > "/run/libvirt/libvirt-sock" > # define LIBVIRTD_PRIV_UNIX_SOCKET_RO LOCALSTATEDIR > "/run/libvirt/libvirt-sock-ro" > To > # define LIBVIRTD_PRIV_UNIX_SOCKET "/var" "/run/libvirt/libvirt-sock" > # define LIBVIRTD_PRIV_UNIX_SOCKET_RO "/var" "/run/libvirt/libvirt-sock-ro" > > Fixed the problem and things worked fine. > > It would be nice for a client only builds to be able to control through a > ./configure argument or through some other .conf file where the server > expects to find its socket file. But you DO have that capability: ./configure --localstatedir=/var > > That said, I am wondering why the client has to know where the server > maintains its libvirt-sock files? Can't client and the server both talk in > relative path terms instead of absolute? You're welcome to propose a patch along those lines. -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ libvirt-users mailing list libvirt-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvirt-users
