This is a bug that I have not had time to pursue...
Configure Apache 2.0 for Windows to pipe access logs through rotatelogs. Start up
apache.
Whack the child process unnaturally :-). The server stops responding to requests (even
though child process was restarted). Take Apache down then bring it back up. Server
still
does not respond to requests. netstat -an shows two listeners to port 80 and this is
why
the server is not responding. Take Apache completely down. Still have a listener on
port
80!!
Notice that a rotatelogs.exe is still hanging around from the unnatural whack (this is
a
bug that we do not clean up rotatelog) and lill it. Listener on port 80 is gone.
Apparently rotatelog inherited the HTTP Server listening socket, which is a bit strange
because I don't think it can actually be used by rotatelogs.
I may be able to look at this next week if no one wants to look at it before then.
Bill
