Comments inline On 3/7/13 1:01 PM, "Eric Blake" <eblake@xxxxxxxxxx> wrote: >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 > Yes. That¹s what Daniel suggested and it errors during install because I don't have root access and I am trying to install it into /users/sarvi/mytools for a personal install that doesn't affect all the users on the machine. ./configure --prefix=/users/sarvi/mytools --localstatedir=/var --sysconfdir=/etc This is the libvirt remote client only and from what I see it can maintain its own client side state under /users/sarvi/mytools as well and would probably be preferred. Having to change the client side install locations to match the different server side install locations seems inconvenient in this use case. Sarvi > >> >> 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 > _______________________________________________ libvirt-users mailing list libvirt-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvirt-users
