From nobody@hyperreal.com  Mon May 26 06:32:59 1997
Received: (from nobody@localhost)
	by hyperreal.com (8.8.5/8.8.5) id GAA29863;
	Mon, 26 May 1997 06:32:59 -0700 (PDT)
Message-Id: <199705261332.GAA29863@hyperreal.com>
Date: Mon, 26 May 1997 06:32:59 -0700 (PDT)
From: Lars Eilebrecht <sfx@unix-ag.org>
Reply-To: sfx@unix-ag.org
To: apbugs@hyperreal.com
Subject: Graceful restart does not work.
X-Send-Pr-Version: 3.2

>Number:         621
>Category:       os-ultrix
>Synopsis:       Graceful restart does not work.
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          closed
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Mon May 26 06:40:01 1997
>Last-Modified:  Sun Jun 22 21:27:39 PDT 1997
>Originator:     sfx@unix-ag.org
>Organization:
>Release:        1.2b10
>Environment:
Ultrix 4.4 MIPS
>Description:
Doing a 'kill -16 PID' on my Ultrix machine does not work.
The error.log shows the messages:
"SIGUSR1 received.  Doing graceful restart" and "Server configured -- resuming normal operations",
but the config file isn't reread rsp. the server isn't restarted (as shown
by mod_status).

>How-To-Repeat:

>Fix:

>Audit-Trail:
State-Changed-From-To: open-closed
State-Changed-By: dgaudet
State-Changed-When: Sun Jun 22 21:27:39 PDT 1997
State-Changed-Why:
As documented in the htdocs/manual/stopping.html page a graceful
restart does not reset the scoreboard.  A better test would
be to look at the children pids before and after the restart.
Ultrix is one of those architectures with unreliable restarts
though ... because it requires a scoreboard file.  The docs talk
about that.

Thanks for the report.

Dean
>Unformatted: