Subject: | |
From: | |
Reply To: | |
Date: | Thu, 4 Sep 2008 16:04:50 +0200 |
Content-Type: | multipart/signed |
Parts/Attachments: |
|
|
Hi Robert,
> I have installed nss_ldap-253-13.el5_2.1.i386 from sl-fastbugs and set
> ssl off (/etc/ldap.conf).
>
> I tested with bind_policy hard (/etc/ldap.conf) and the server still
> tries to connect to an ldap server before either interface lo or eth0
> are up.
>
> I am looking at /etc/udev/rules.d/50-udev.rules to see if their are any
> device not in my /etc/group.??... (I'm still fishing for a solution.)
Could it be possible that there is a console lock in /var/run/console ?
At least during a crash it will not be removed, and I fear that
pam_console often will not remove it also during a normal logout.
udev then tries to retrieve the uid of the the user.
A hack as fix for this problem (but definitly not a perfect solution),
would be to remove the locks in /var/run/console before udev starts. But
be aware that at this point the system is readonly mounted, so a remount
is necessary:
# Remove files in /var/run/console to avoid udev hung
# Have to remount rw temporarily as filesystem is not yet writeable
# There should be another fix in udev or pam_console_apply at the long run
mount -o remount,rw /
rm -f /var/run/console/*
mount -o remount,ro /
Put these lines into /etc/rc.d/rc.sysinit just before /sbin/start_udev
and try it out.
I have this hack built into my desktop systems, as we had some hung
situations during bootstrap with udev.
Sincerly,
Klaus
|
|
|