Red Hat Bugzilla – Bug 67753
ldap is started too late in the boot process. Needs to be sooner than autofs since autofs can load its config based on it.
Last modified: 2014-08-31 19:24:16 EDT
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):
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
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.
This bug is still present in RedHat 8.0.
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.
This bug is also still present in both Fedora Core 2 and 3.
According to the CVS log, this was fixed in Fedora Core 4.