Bug 692594

Summary:	/etc can be read only
Product:	[Fedora] Fedora	Reporter:	Bill Nottingham <notting>
Component:	samba	Assignee:	Guenther Deschner <gdeschner>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	15	CC:	dpal, gdeschner, jlayton, rvokal, ssorce
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	samba-3.5.8-68.fc15.1	Doc Type:	Bug Fix
Doc Text:	Prior to this update, Samba could fail to start when the /etc/ directory was a read-only file system. This occurred because Samba checked at start-up if the user had write permissions to the /etc/samba/smb.conf file. With this update, Samba checks if the root user is running the start-up script. Now Samba is started successfully when run by the root user.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-04-14 13:42:40 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	692326

Description Bill Nottingham 2011-03-31 16:07:24 UTC

Description of problem:

/etc/init.d/smb and /etc/init.d/nmb:

# Check that we can write to it... so non-root users stop here
[ -w /etc/samba/smb.conf ] || exit 4

/etc is allowed to be read-only, and samba should still run in this case.

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

3.6.0

Comment 1 Simo Sorce 2011-04-06 15:59:10 UTC

Günther pushed a fix on Monday, should be fixed when the package gets to stable.

Comment 2 Eva Kopalova 2011-05-04 14:03:19 UTC

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Prior to this update, Samba could fail to start when the /etc/ directory was a read-only file system. This occurred because Samba checked at start-up if the user had write permissions to the /etc/samba/smb.conf file. With this update, Samba checks if the root user is running the start-up script. Now Samba is started successfully when run by the root user.