I am writing a PAM module that needs to spawn a child, and eventually reap the child when it terminates. Are there any conventions, restrictions or limits on setting a SIGCHLD handler (or any signal handler) within a PAM module? How does one prevent another pam module (that also spawns a child...) from interfering with another? I haven't been able to find any documentation on this subject - any input would be appreciated. Thanks! Doug Fajardo _______________________________________________ Pam-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/pam-list