SCIENTIFIC-LINUX-USERS Archives

May 2008

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Jan Iven <[log in to unmask]>
Reply To:
Date:
Sun, 25 May 2008 10:21:41 +0200
Content-Type:
text/plain
Parts/Attachments:
text/plain (20 lines)
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

ATOM RSS1 RSS2