From: Nuno Monteiro <nuno.monteiro@ptnix.com>
To: Zwane Mwaikambo <zwane@arm.linux.org.uk>
Cc: "Randy.Dunlap" <rddunlap@osdl.org>, Edward Tandi <ed@efix.biz>,
linux-kernel@vger.kernel.org, Valdis.Kletnieks@vt.edu
Subject: Re: woes with 2.6.0-test1 and xscreensaver/xlock
Date: Wed, 16 Jul 2003 22:00:59 +0100 [thread overview]
Message-ID: <20030716210059.GA1564@hobbes.itsari.int> (raw)
In-Reply-To: <20030716195656.GA1567@hobbes.itsari.int>; from nuno.monteiro@ptnix.com on Wed, Jul 16, 2003 at 20:56:56 +0100
[-- Attachment #1: Type: text/plain, Size: 674 bytes --]
On 2003.07.16 20:56, Nuno Monteiro wrote:
>
>
[bla bla bla snipped]
Replying to myself:
Ok, I figured it out. It's a definitely a pam problem. I fetched latest
pam rpm from RH RawHide and picked up their sigchld patch, applied it to
mandrake cookers's latest pam package, rebuilt, et voila'. All is well
again, it doesnt hang anymore. I think the bug in bugzilla can be closed
now. I'm attaching the patch to pam 0.77, if anyone wants to give it a
spin. Also, should anyone from mandrake is reading this, it'd be
adviseable to apply it to the official package. I'll ping them anyway, to
let them know of this.
Thanks for the input, everyone.
Regards,
Nuno
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: pam-0.77-sigchld.patch --]
[-- Type: text/x-diff; charset=unknown-8bit, Size: 950 bytes --]
Specifying SIG_IGN for SIGCHLD (which by default, is ignored) is not the same
as specifying SIG_DFL. See the NOTES section of wait(2) for the skinny on this.
--- Linux-PAM-0.77/modules/pam_pwdb/support.-c 2003-07-09 00:15:06.000000000 -0400
+++ Linux-PAM-0.77/modules/pam_pwdb/support.-c 2003-07-09 00:15:19.000000000 -0400
@@ -370,7 +370,7 @@
* The "noreap" module argument is provided so that the admin can
* override this behavior.
*/
- sighandler = signal(SIGCHLD, SIG_IGN);
+ sighandler = signal(SIGCHLD, SIG_DFL);
}
/* fork */
--- Linux-PAM-0.77/modules/pam_unix/support.c 2003-07-09 00:15:29.000000000 -0400
+++ Linux-PAM-0.77/modules/pam_unix/support.c 2003-07-09 00:15:41.000000000 -0400
@@ -597,7 +597,7 @@
* The "noreap" module argument is provided so that the admin can
* override this behavior.
*/
- sighandler = signal(SIGCHLD, SIG_IGN);
+ sighandler = signal(SIGCHLD, SIG_DFL);
}
/* fork */
next prev parent reply other threads:[~2003-07-16 20:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-16 17:27 Nuno Monteiro
2003-07-16 18:02 ` Edward Tandi
2003-07-16 18:58 ` Zwane Mwaikambo
2003-07-16 19:16 ` Randy.Dunlap
2003-07-16 19:13 ` Zwane Mwaikambo
2003-07-16 19:33 ` jjs
2003-07-16 19:32 ` Valdis.Kletnieks
2003-07-16 19:56 ` Nuno Monteiro
2003-07-16 21:00 ` Nuno Monteiro [this message]
2003-07-16 20:17 ` jhigdon
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=20030716210059.GA1564@hobbes.itsari.int \
--to=nuno.monteiro@ptnix.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=ed@efix.biz \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
--cc=zwane@arm.linux.org.uk \
/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
all inboxes | Powered by JetHome®