Bug 1124066 - incorrect run directory for samba vfs EPEL RPMS
Summary: incorrect run directory for samba vfs EPEL RPMS
Keywords:
Status: CLOSED EOL
Alias: None
Product: GlusterFS
Classification: Community
Component: unclassified
Version: pre-release
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-07-28 22:18 UTC by Paul Robert Marino
Modified: 2015-10-22 15:40 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-10-22 15:40:20 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)

Description Paul Robert Marino 2014-07-28 22:18:35 UTC
Description of problem:
with the samba 4 vfs RPMS here http://download.gluster.org/pub/gluster/glusterfs/samba/RHEL/epel-6Server/ the path for the pid dir and sockets dir are incorrect.
In the spec file they are set to /run and /run/samba this is incorrect.


Version-Release number of selected component (if applicable):


How reproducible:
absolute

Steps to Reproduce:
1. service smb start
2. service smb status
3. grep -R '/run' /var/log/samba

Actual results:

Samba crashes because there is no /run or /run/samba direectory

Expected results:

the smb service should start up normally

Additional info:

A simple workaround is to create a symlink "ln -s /var/run /run"
then create a /var/run/samba directory

the actual fix would be to change these lines in the spec file
from
"
        --with-piddir=/run \
        --with-sockets-dir=/run/samba \
"
to
"
        --with-piddir=/var/run \
        --with-sockets-dir=/var/run/samba \
"

Comment 1 Kaleb KEITHLEY 2015-10-22 15:40:20 UTC
pre-release version is ambiguous and about to be removed as a choice.

If you believe this is still a bug, please change the status back to NEW and choose the appropriate, applicable version for it.


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