Mailinglist Archive: opensuse-features (188 mails)

< Previous Next >
[New: openFATE 309148] boot-process: starting network / dbus with ldap authentification
  • From: fate_noreply@xxxxxxx
  • Date: Mon, 8 Mar 2010 12:54:48 +0100 (CET)
  • Message-id: <feature-309148-1@xxxxxxxxxxxxxx>
Feature added by: Alexander Fleischer (afleischer)

Feature #309148, revision 1
Title: boot-process: starting network / dbus with ldap authentification

openSUSE-11.3: Unconfirmed
Priority
Requester: Important

Requested by: Alexander Fleischer (afleischer)

Description:
I asked to file this bug report as feature request:
https://bugzilla.novell.com/show_bug.cgi?id=569953
(https://bugzilla.novell.com/show_bug.cgi?id=569953)

After configuring LDAP authentification via yast the system needs about 20
minutes to start the dbus-daemon on boot. I got a lot of ldap messages in
/var/log/messages like these:
Jan 12 12:01:44 w2 dbus-daemon: nss_ldap: failed to bind to LDAP server
ldaps://10.0.0.10: Can't contact LDAP server
Jan 12 12:01:44 w2 dbus-daemon: nss_ldap: reconnecting to LDAP server (sleeping
8 seconds)...

Of course, because network is started after dbus, dbus can't connect to the
ldap server, and waits several times until the timeout is reached.

Network has dbus as "required-start", so i can't change the startup order and
add $network to required-start in the dbus script.

My temporary solution is to replace the /etc/nsswitch.conf file with a one
without ldap access in /etc/init.d/boot.local and restoring the original one
after the network is up.
But this is not a clean solution, maybe an extra startup script can solve the
problem.

--
openSUSE Feature:
https://features.opensuse.org/309148

< Previous Next >
List Navigation
This Thread
Follow Ups
References