https://bugzilla.novell.com/show_bug.cgi?id=348318
User jtorres@caci.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=348318#c9
Jose Torres
Hello I have the same problem. We use ldap for user authentication. After booting the client, it needs about 30 minutes to boot. /var/log/messages shows lines for reconnecting for the ldap server.
Your solution above does not work for me. Because insserv -r /etc/init.d/dbus complains "loop exists for network". I can change the boot order manually, but I think when I install some updates, the boot order will be the same like before.
My question is: Why does the system want connect to the ldap server, and doesn´t look to the local passwd file. At the moment the client hangs, it want likely start the consolekit daemon.
Greetings George
Here's what (In reply to comment #4 from Thomas Voigt)
My solution:
Changed the line
# Required-Start: $local_fs
in /etc/init.d/dbus into
# Required-Start: $local_fs $network
and did a "insserv -r /etc/init.d/dbus" and a "insserv /etc/init.d/dbus".
So the starting order is now
lrwxrwxrwx 1 root root 7 Dec 14 10:38 /etc/rc.d/rc3.d/S06dbus -> ../dbus lrwxrwxrwx 1 root root 13 Dec 14 10:38 /etc/rc.d/rc3.d/S07consolekit -> ../consolekit lrwxrwxrwx 1 root root 10 Dec 14 10:38 /etc/rc.d/rc3.d/S07network -> ../network
Don't know why, but this works for me.
It seem like more of a general Linux problem. I had the same situation with the Fedora distributions. Here's what I did was to make it work. cd /etc cp nsswitch.conf nsswitch-orig.conf Use yast to configure LDAP. This will create a new nsswitch.conf file. cp nsswitch.conf nsswitch-ldap.conf cd /etc/init.d Used the attached ldap.patch file. patch -p0 < ldap.patch Reboot. Everything works. Its a terrible hack, but it got me going. Hope this helps!!! Jose -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.