mod_cgi/3079: Sending a SIGUSR1 to daemon propogates to CGI children

[Ken Mayer <kl...@bitwrangler.com>]

>Number:         3079
>Category:       mod_cgi
>Synopsis:       Sending a SIGUSR1 to daemon propogates to CGI children
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Fri Sep 25 15:40:02 PDT 1998
>Last-Modified:
>Originator:     klm@bitwrangler.com
>Organization:
apache
>Release:        
>Environment:
FreeBSD 2.2.6
>Description:
During the run of a cgi script, the web server receives a SIGUSR1 (graceful shutdown and reload). This signal is propogated to all members of the process group, include the cgi process. Not expecting a signal, the cgi process dies. Is this a reasonable thing to expect? SIGUSR1 will almost certainly not have the same semantics for the CGI as it does for the server. 
>How-To-Repeat:
write a quick cgi script that sleeps for 30 seconds, call it, meanwhile send 
SIGUSR1 to the web server daemon.
>Fix:
call setsid inside spawn_child... ?
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <ap...@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]
[If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request ]
[from a developer.                                      ]
[Reply only with text; DO NOT SEND ATTACHMENTS!         ]