Bug 67753

Summary:	ldap is started too late in the boot process. Needs to be sooner than autofs since autofs can load its config based on it.
Product:	[Retired] Red Hat Linux	Reporter:	Bill Peck <bill>
Component:	openldap	Assignee:	Jay Fenlason <fenlason>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Aaron Brown <abrown>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.3	CC:	jfeeney, stephen.walton, steve
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	openldap-2_2_23-2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-01-11 17:00:59 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 Bill Peck 2002-07-01 17:03:45 UTC

From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)

Description of problem:
I have a server installed with openldap-2.0.23-4 and the startup order is set 
to 39.  This is much too late in the boot sequence since autofs starts at 28. 
This is fine for all the client machines but the server does not load its auto 
mount entries because ldap is not running when autofs starts.

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


How reproducible:
Always

Steps to Reproduce:
1. install openldap and autofs
2. configure ldap to serve automount entries for autofs
3. reboot the server machine.  automount will run and complain of no maps.
	

Actual Results:  autofs doesn't load the servers automount maps.

Expected Results:  ldap should be running and autofs should load the automount 
maps

Additional info:

I have manually changed the boot sequence for openldap to be before autofs and 
have not had any ill effects from this change.

Please consider fixing this in a later release.

Thanks!

Comment 1 Stephen Walton 2003-02-15 00:17:45 UTC

This bug is still present in RedHat 8.0.

Comment 2 Stephen Walton 2003-02-15 00:24:43 UTC

Sorry, one more comment:  In addition to starting ldap before autofs, ldap needs
to be stopped after autofs, otherwise system shutdown fails.  I changed the
chkconfig line in /etc/rc.d/init.d/ldap to '# chkconfig: 345 27 73' so that it
starts right before autofs and stops right after.

Comment 3 Steven Pritchard 2005-05-02 17:02:06 UTC

This bug is also still present in both Fedora Core 2 and 3.

Comment 4 Jay Fenlason 2006-01-11 17:00:59 UTC

According to the CVS log, this was fixed in Fedora Core 4.