RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 886157 - samba4 should use the same winbind pipes as samba
Summary: samba4 should use the same winbind pipes as samba
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: samba4
Version: 6.4
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: rc
: ---
Assignee: Andreas Schneider
QA Contact: Namita Soman
URL:
Whiteboard:
Depends On:
Blocks: 888457
TreeView+ depends on / blocked
 
Reported: 2012-12-11 16:15 UTC by Sumit Bose
Modified: 2013-02-21 08:46 UTC (History)
2 users (show)

Fixed In Version: samba4-4.0.0-51.el6.rc4
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-21 08:46:27 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2013:0506 0 normal SHIPPED_LIVE Moderate: samba4 security, bug fix and enhancement update 2013-02-20 21:30:25 UTC

Description Sumit Bose 2012-12-11 16:15:56 UTC
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

Comment 2 Andreas Schneider 2012-12-12 14:39:21 UTC
I will add --with-winbindd-socket-dir=/var/run/winbindd

Comment 4 Namita Soman 2013-01-28 18:18:34 UTC
# 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

Comment 5 errata-xmlrpc 2013-02-21 08:46:27 UTC
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


Note You need to log in before you can comment on or make changes to this bug.