Consider adding --with-winbindd-socket-dir

[Andrew Bartlett]

On Mon, 2012-10-01 at 12:49 +0300, Alexander Bokovoy wrote:
> Hi,
> 
> there seem to be disparity in defining where winbindd socket directory
> should be in git master. In dynconfig/wscript we define
> --with-sockets-dir that is used directly for smbd and derive
> winbindd's socket directory out of it as ${SOCKET_DIR}/winbindd. If
> one uses --with-sockets-dir=/var/run/samba, for example, then
> winbindd's socket directory will be /var/run/samba/winbind.
> 
> This is all fine unless you are dealing with co-install of samba 3.6
> and samba 4.x on the same machine. We have such setup in RHEL6 for
> maintenance reasons and building libwbclient only in samba 3.6 build,
> since this is the same library in both samba 3.6 and 4.x cases. Samba
> 3.6 in RHEL6 is built with --with-sockets-dir=/var/run, for various
> historical reasons.

I'm a little confused.  Except as a build dep, what is the runtime use
of the private libwbclient from master in your configuration?  

That is, why does this matter?  (I didn't think you were packaging the
server-side components)

Thanks,

Andrew Bartlett

-- 
Andrew Bartlett                                http://samba.org/~abartlet/
Authentication Developer, Samba Team           http://samba.org