Red Hat Bugzilla – Bug 886157
samba4 should use the same winbind pipes as samba
Last modified: 2013-02-21 03:46:27 EST
Description of problem: samba4 is configured with the option --with-sockets-dir=/var/run/samba which places the public winbind socket in /var/run/samba/winbindd/pipe . The samba based on samba3 has a patch (samba-3.2.0pre1-pipedir.patch) to create the socket as /var/run/winbindd/pipe. samba4 should use tha same path to not break existing components like e.g. SELinux labeling. Version-Release number of selected component (if applicable): samba4-4.0.0-50.el6.rc4
I will add --with-winbindd-socket-dir=/var/run/winbindd
# rpm -qa | grep samba samba4-libs-4.0.0-53.el6.rc4.x86_64 samba4-common-4.0.0-53.el6.rc4.x86_64 samba4-4.0.0-53.el6.rc4.x86_64 samba4-python-4.0.0-53.el6.rc4.x86_64 samba4-winbind-clients-4.0.0-53.el6.rc4.x86_64 samba4-winbind-4.0.0-53.el6.rc4.x86_64 Verified that /var/run/samba/winbindd/pipe does not exist, and instead is at /var/run/winbindd/pipe # ls -l /var/run/samba/ total 8 -rw-------. 1 root root 1307 Jan 28 09:58 krb5cc_samba drwxr-xr-x. 3 root root 4096 Jan 28 12:14 ncalrpc # ls -l /var/run/winbindd/pipe srwxrwxrwx. 1 root root 0 Jan 28 12:14 /var/run/winbindd/pipe
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2013-0506.html