Mailing-List: contact modules-dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: modules-dev@httpd.apache.org
Received-SPF: pass (herse.apache.org: domain of djwortham@gmail.com designates
 64.233.166.177 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:mime-version:content-type;
        b=s9vueIrH+j3bxRU/v+jULEoI+tM+mP6w1Nv9F3GdbEdU8SexGIYPvaSB7QB/LoAntw2inhu3d9T6PQp10fZ920CDA/trV3KXUeIqeS5eWBhKB8ujBxgD9F2Btw1mxP9bOuTbmKlF6n7VSa2qm/ZTg08IwOKXmJdOJ0BdgOHEL18=
Message-ID: <5280fae50701081937x20967e1bv4fcae416dde27c01@mail.gmail.com>
Date: Mon, 8 Jan 2007 20:37:52 -0700
From: "David Wortham" <djwortham@gmail.com>
To: modules-dev@httpd.apache.org
Subject: Server Restarts
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_48232_31415423.1168313872378"

------=_Part_48232_31415423.1168313872378
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi guys,
I know Nick or one of the other frequent responders mentioned something
about a double server-startup.  Does anyone have (or know of) documentation
on this effect?  I believe I understand the relationships between the server
process, the child processes and the cprocess threads.

It seems like I always have to restart one extra time (first restart is
always a dud... as if the server daemon was not running) after re-compiling
the module (with apxs).  Recently, I get whitescreens on the second restart
and now have to restart a total of 3 times after every re-compile (also
requires me to restart once after the initial daemon startup).  This won't
make sysadmins very happy to use my module if I require them to restart
their webserver twice every time they need to reload it.

Did I foul something up or is this normal/expected?

Thanks,
Dave

------=_Part_48232_31415423.1168313872378--