Thanks for the answers
>>>>> On Tue, 24 Jun 2008 15:51:37 -0400
>>>>> "MS" == Meenoo Shivdasani <meenoo@xxxxxxxxx> wrote:
MS> On Tue, Jun 24, 2008 at 3:44 PM, Johnny Hughes
MS> <johnny@xxxxxxxxxx> wrote:
>> There is a BUG with nss_ldap:
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=448014
>>
>> We have this bug listed in our release notes:
>>
>> http://wiki.centos.org/Manuals/ReleaseNotes/CentOS5.2#head-447967c60eb305ef2c5dbbc3f4e8b3c4c5170632
I read that, but I didn't connect it to my bug, because I didn't think
that anything to do with bash is relevant at that time during the boot
process. But obviously I was wrong (and by the way: that problem also
occurs with 5.1, so I don't think that it is a bash 3.2 problem)
>> You can try the nss_ldap from our testing repo for this bug:
>>
>> http://dev.centos.org/centos/5/
>>
>> This may help with the problem.
MS> FWIW, my experience with a variant of this problem and
MS> nss_ldap from the testing repo was that boot would hang
MS> indefinitely at udevd unless I limited the nss_reconnect_*
MS> values. I ended up changing to bind_policy soft as a
MS> workaround.
So the bottom line is
- it is possible to shave 2 min off the boot process
- a good chance to make the machine unbootable (and then play around
until it works)
Well, I'm a lazy coward ;) but thanks
Bernhard
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
