There is a bad interaction with the pam packages that are currently being shipped with mdk 9.1 and cooker, and kernels 2.5 and 2.6. The pam_unix module hangs xscreensaver and xlock whenever the user types his/hers password to get the session back. Redhat folks have a patch for this problem in their tree, its on their pam-0.77-2.src.rpm package, and its called pam-0.77-sigchld.patch. I'm attaching it to this email for convenience, as I believe it should be merged with mdk's pam package too. I'm currently running a custom pam-0.77-2mdk with it applied on a 2.6.0-
test1 kernel and it works withou any hisses. Without it, I simply cannot use 'xscreensaver lock' or 'xlock'.
This problem has been discussed on lkml (http://marc.theaimsgroup.com/?
t=105837695800007&r=1&w=2) today and I believe around may 31st too, possibly on other occasions as well.
Please review and comment, thanks. Disregard it if this has been debated before, I couldnt find any relevant mentions to it on the archives.
Regards,
Nuno
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 */
