Foo Ji-Haw wrote:
I am trying my luck again on this issue, which I never quite understood/
resolved.
The log file shows this when Apache starts:
1 (parent/healthcheck process)
2 (parent/healthcheck process)
1 (child/real server process)
2 (child/real server process)
In 1.3, the child 'owned' the logs and overwrote everthing. 2.0 uses locking
to allow the parent's log entries to be preserved.
The win32 'parent' never serves a request. It's resources are also not really
inherited by the child, so each child must 'do it's own thing' with respect to
fully initializing the server.
And the log file shows this when Apache restarts:
3 (parent/healthcheck process)
1 (child/real server process)
2 (child/real server process)
The parent signals the 'old child' to begin to shut down (and quit listening
for new connections) while it spawns up a new full blown child process, with
the same child behavior as you noted on first-start.
