hey ged
yestserday i saw the post that you referenced. if i understand that post, the user was noticing that when the initial httpd process is started, it forks to create another httpd root process. the PID for this 2nd root httpd process is written to the webserver's PID file and this 2nd root httpd process then spawns the children to handle requests. when a USR2 is sent to this 2nd root httpd process, the logging in startup.pl shows that the PID that rec'd the USR2 was the initial root process (which no longer appears as an active process in the process table) rather than the 2nd root httpd process. definitely confusing.
in my testing, i see the same situation happening on a solaris machine: the initial root httpd process forks to create a 2nd root httpd process, the PID for 2nd root httpd is written to the webserver's PID file; startup.pl has a USR2 sig handler that logs the PID of the receiving process; when i send a USR2 to this 2nd root httpd process, the handler is executed and i see that the receiving PID is actually the initial root PID which isn't visible in the process table.
anyway, the signal handler is working on solaris. my problem is that on my linux setup the signal handler is being completely ignored. i send a USR2 to the root httpd process and the signal handler is not executed at all...
