Hi Guys,

I've been able to setup an ldap server and it works at the linux client with no problem. However, I want also that my ldap server would leverage LDAP authentication. What I did was the same steps that I did from the clients since the server is Fedora 5 and I went to setup authentication from the gui. However, after restart (to see the effect of change). Named and system messages bus services takes forever to startup during boot time processes. I found out from googling that problem arises from nsswitch.conf which takes time to read from ldap lines. Problem resolved by omitting ldap entry at nsswitch.conf. I need clarification why this is happenning from ldap server and not from the clients. Are there other way to make this thing works?

thanks..... any weird suggestions are welcome...

I would assume that it is due to the order in which the services are being started. i'd expect that the message bus would start a lot earlier on than slapd, and possibly the same for named. am i right in assuming that if you restart named once you're up and running that it goes just fine? you could easily push slapd further up the rungs in terms of boot priority, but that could theoretically lead into interdependence issues. but essentially the subsystem is trying to reach an ldap server which is not yet running, unlike the clients which obviously just hit the ldap server fine each time.

I'm not aware of any way to fine tune this behaviour to be honest. if you can't move the slapd service up, i'm not sure what your options are - replacing the nsswitch.conf file automatically once slapd starts? but then, servers aren't designed to boot fast, they;re designed to start up once and stay started!