Bug 493022

Summary:	winbind needs to be started before netfs
Product:	Red Hat Enterprise Linux 5	Reporter:	Sachin Prabhu <sprabhu>
Component:	samba	Assignee:	Guenther Deschner <gdeschner>
Status:	CLOSED WONTFIX	QA Contact:	qe-baseos-daemons
Severity:	medium	Docs Contact:
Priority:	low
Version:	5.3	CC:	dpal, gdeschner, tao
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	592984 (view as bug list)		Environment:
Last Closed:	2010-05-17 14:38:58 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	502912, 592984

Description Sachin Prabhu 2009-03-31 11:26:57 UTC

To mount Windows shares at boot time, we need to add it to fstab. If we pass the uid,gid mount options pointing to an AD user to define the owner and group for files on the share, winbind must be started before netfs.

//<host name >/samba2 /mnt/smb2 cifs user=example.com/test,credentials=/etc/test.credentials,rw,uid=test,gid=test 0 0

On RHEL 5, the start priority for netfs is #25 and for winbind it is  under # 91. 

To work around the problem, we would need to change the start priority for netfs or winbind manually.

Comment 1 Simo Sorce 2009-03-31 12:40:24 UTC

Not so simple, while winbindd can use cached data it needs the network too.
Have you tested moving winbindd before netfs? Does it work correctly ?

Comment 2 Simo Sorce 2009-03-31 12:44:41 UTC

Sorry I read netfs and parsed "network".
However is /usr/sbin always certainly available when netfs is started ?

Comment 5 Dmitri Pal 2010-05-17 14:38:58 UTC

There is a workaround to change levels in the init script manually. 
We will try to address this issue in 6.1. No plans for 5.x closing as won't fix.