Bug: dsee_directory should launch prior to ldap.client
Hello. Recently switched my directory from OpenLDAP to Sun. Works great, but I noticed today when the server had to be rebooted that the boot process stopped on the ldap.client init script. This was because the client is /etc/rc2.d/S71ldap.client, but the directory is at /etc/rc2.d/S72dsee_directory. I put it into single-user and moved dsee_directory from S72 to S70. Everything works great now, but this should be submitted as a bug affecting systems authenticating against their own LDAP server.
# 2
In the past, Sun has advised against having LDAP servers be "clients of themselves" for naming service.
I would guess the reasoning is deeper than just the ordering of the startup scripts. But I don't know what the reasons were, or if they're still applicable.
Any experts out there who can update us on this?
# 3
I had never had a problem with ldap.client connecting to an OpenLDAP server that was spawned prior to it. When I switched to dsee_directory, it just sat on the ldap client script trying to connect. The ordering did fix my boot issue. However, I had never heard Sun advises against LDAP client of themselves. This kind of baffles me since other operating systems typically do this (Linux, Active Directory, etc...). At any rate, it works great now, but I am curious as to why Sun would discourage this setup. BTW, this is DSEE 6 and Solaris 9/sparc.
