Received: (qmail 11507 invoked by uid 2012); 10 Jun 1998 15:09:03 -0000
Message-Id: <19980610150903.11506.qmail@hyperreal.org>
Date: 10 Jun 1998 15:09:03 -0000
From: Lars Kellogg-Stedman <lars@bu.edu>
Reply-To: lars@bu.edu
To: apbugs@hyperreal.org
Subject: Apache isn't responding correctly to SIGHUP.
X-Send-Pr-Version: 3.2

>Number:         2405
>Category:       os-irix
>Synopsis:       Apache isn't responding correctly to SIGHUP.
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    apache
>State:          closed
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Wed Jun 10 08:10:01 PDT 1998
>Last-Modified:  Fri Nov  6 10:15:51 PST 1998
>Originator:     lars@bu.edu
>Organization:
>Release:        1.3.0
>Environment:
IRIX buit3 6.3 12161207 IP32
>Description:
On my system (Irix 6.3, reasonably current as far as patches go), Apache
doesn't restart when it receives a SIGHUP.  All of the child servers die,
but nothing comes back up.  The main server process continues to run, but
it doesn't respond to any incoming requests, nor does it log any errors
to the error_log.
>How-To-Repeat:

>Fix:

>Audit-Trail:

From: Dean Gaudet <dgaudet@arctic.org>
To: Lars Kellogg-Stedman <lars@bu.edu>
Cc: apbugs@hyperreal.org
Subject: Re: os-irix/2405: Apache isn't responding correctly to SIGHUP.
Date: Wed, 10 Jun 1998 13:53:50 -0700 (PDT)

 Try adding:
 
 EXTRA_CFLAGS=-DUSE_FCNTL_SERIALIZED_ACCEPT
 
 or 
 
 EXTRA_CFLAGS=-DUSE_USLOCK_SERIALIZED_ACCEPT
 
 to your src/Configuration file and recompiling.  Tell us how it goes,
 thanks.
 
 Dean
 
State-Changed-From-To: open-feedback
State-Changed-By: lars
State-Changed-When: Tue Jul  7 15:59:10 PDT 1998
State-Changed-Why:
[switching to feedback state]
Comment-Added-By: lars
Comment-Added-When: Fri Oct  9 18:58:02 PDT 1998
Comment-Added:
[This is a standard response.]
This Apache problem report has not been updated recently.
Please reply to this message if you have any additional
information about this issue, or if you have answers to
any questions that have been posed to you.  If there are
no outstanding questions, please consider this a request
to try to reproduce the problem with the latest software
release, if one has been made since last contact.  If we
don't hear from you, this report will be closed.
If you have information to add, BE SURE to reply to this
message and include the apbugs@Apache.Org address so it
will be attached to the problem report!
State-Changed-From-To: feedback-closed
State-Changed-By: lars
State-Changed-When: Fri Nov  6 10:15:51 PST 1998
State-Changed-Why:
[This is a standard response.]
No response from submitter, assuming issue has been resolved.
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <apbugs@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]