Bug 488774

Summary: autofs starting before ypbind
Product: [Fedora] Fedora Reporter: Michael Young <m.a.young>
Component: autofsAssignee: Jeff Moyer <jmoyer>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: ikent, jmoyer
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-03-13 02:59:19 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:

Description Michael Young 2009-03-05 17:52:19 UTC 
If NetworkManager, ypbind and autofs are installed, chkconfig decides that, based on the ### BEGIN INIT INFO sections of NetworkManager and ypbind, that autofs should be started after ypbind, and as a result autofs fails to set up the right mounts. Something like

### BEGIN INIT INFO
# Provides: $autofs
# Required-Start: $network $ypbind
# Required-Stop: $network $ypbind
# Default-Start: 3 4 5
# Default-Stop: 0 1 2 6
# Short-Description: Automounts filesystems on demand
# Description: Automounts filesystems on demand
### END INIT INFO

added to the init script should the problem I am seeing.
Comment 1 Ian Kent 2009-03-13 02:59:19 UTC 

*** This bug has been marked as a duplicate of bug 475002 ***