From: "Kay Sievers" <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev ldap wait
Date: Sat, 25 Aug 2007 14:44:30 +0000 [thread overview]
Message-ID: <3ae72650708250744l5c80de0ete74889bc71094d02@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0708251524500.28540@fbirervta.pbzchgretzou.qr>
On 8/25/07, Jan Engelhardt <jengelh@computergmbh.de> wrote:
> ttyS0 picked this up on boot.
>
> Welcome to Aurora SPARC Linux
> Press 'I' to enter interactive startup.
> Setting clock (localtime): Sat Aug 25 15:21:39 CEST 2007 [ OK ]
> Starting udev: udevd[370]: nss_ldap: failed to bind to LDAP server ldar
> udevd[370]: nss_ldap: failed to bind to LDAP server ldap://127.000.1: Can't conr
> udevd[370]: nss_ldap: reconnecting to LDAP server (sleeping 4 seconds)...
> udevd[370]: nss_ldap: failed to bind to LDAP server ldap://127.0.0.1: Can't conr
> udevd[370]: nss_ldap: reconnecting to LDAP server (sleeping 8 seconds)...
> udevd[370]: nss_ldap: failed to bind to LDAP server ldap://127.0.0.1: Can't conr
> udevd[370]: nss_ldap: reconnecting to LDAP server (sleeping 16 seconds)...
> udevd[370]: nss_ldap: failed to bind to LDAP server ldap://127.0.0.1: Can't conr
> udevd[370]: nss_ldap: reconnecting to LDAP server (sleeping 32 seconds)...
>
> Well, that happens if you have 'bind_policy hard_open' in
> /etc/ldap.conf. Looks like a bad idea, I admit. But does udev really
> need to getpwfoo()?
Make sure, that all the system users and groups, used in udev rules,
exist in the local database, and that the local files are used before
you lookup any other directory service. It will not even try to use
the network, just like /etc/hosts can prevent dns lookups. System
users and groups should exist on the local machine for various
reasons, it's not only udev that has problems with it.
Kay
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2007-08-25 14:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-25 13:29 udev ldap wait Jan Engelhardt
2007-08-25 14:44 ` Kay Sievers [this message]
2007-08-25 14:57 ` Jan Engelhardt
2007-08-25 15:51 ` Kay Sievers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3ae72650708250744l5c80de0ete74889bc71094d02@mail.gmail.com \
--to=kay.sievers@vrfy.org \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox