You are viewing a plain text version of this content. The canonical link for it is here.

Posted to bugs@httpd.apache.org by bu...@apache.org on 2002/09/12 18:24:02 UTC

DO NOT REPLY [Bug 12583] New: - First piped log process do not handle SIGTERM

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12583>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12583

First piped log process do not handle SIGTERM

           Summary: First piped log process do not handle SIGTERM
           Product: Apache httpd-1.3
           Version: 1.3.26
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: mod_log_config
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: cmailloux@wantedtech.com


When the apache server starts piped log process on startup, the signal SIGTERM
is ignored. The new child process inherit of this property. 

Problems occur when we try to stop the apache server. The apache server send a
SIGTERM signal to all children's process. However, the piped log process never
stops because it ignore the SIGTERM signal.

Note : This problem doesn't apply if the piped log process is restarted because
it has die.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org