Hi,

Jeffrey D Anderson wrote:
> On Sunday 25 May 2008 1:21:41 am Jan Iven wrote:
>> On 05/23/2008 07:07 PM, Jeffrey D Anderson wrote:
>> [..]
>>
>>> The "pam_console_apply" signal 13 (broken pipe) is obviously at the core
>>> of the bug, but I don't know enough about pam to really understand what
>>> is going wrong.
>> I would suggest to  set up a test:
>> # strace -s 256 -f -o /tmp/somefile -p <PID_OF_GETTY_ON_CONSOLE>"
>>
>> If you are running nscd, suggest to "strace" this as well.
>>
>> Then repeat your login test, and search the tracefile(s) for signal 13,
>> identify which process held the other end of the pipe, and why it went
>> away - most likely some subprocess died/segfaulted without leaving other
>> traces in the logs.
>>
>> Hope this helps
>> jan
> 
> Thanks for the suggestion.  I ran the strace with both the new, problematic 
> nss_ldap, and the old version that works.  I find three places where broken 
> pipes result.
> 
> Since this is obviously not an SL specific issue, I'm moving my debugging off 
> the list.
> 
> It looks like this is already reported as 
> https://bugzilla.redhat.com/show_bug.cgi?id=447881
> No solution yet, though.

447881 is marked as a duplicate of 448014 
(https://bugzilla.redhat.com/show_bug.cgi?id=448014), and that one does 
have a proposed patch.

Matthias

>