possible solution to log rotation, config reread, shutdown, etc. problem

[Nathan Neulinger <nn...@umr.edu>]

Not sure if this is reasonable, but it seems like it might work.

What about having the master httpd create a unix domain socket that could
be used for control signalling.

A small external program "httpd_ctl" could be used to send control signals
to the master httpd via this socket. This could be used for all control
operations for the server.

It might be worth having a set of configuration directives:

ConfigSocket            On
ConfigSocketFile        logs/config_socket
ConfigSocketUsers       root httpd


Possible operations:
--------------------

httpd_ctl restart - restarts the server, doesn't complete current transactions

httpd_ctl reconfig - rereads configuration files

httpd_ctl suspend - leaves httpd running, finishes all current requests,
then flushes logs, and suspends all activity till the server receives a
resume command.

httpd_ctl resume - resumes server activity

httpd_ctl shutdown - instantly stops all transactions and shuts down the
server. (Currently what would happen when you kill the server.)

httpd_ctl status - queries status of all servers (similar to current status
module)

-- Nathan

------------------------------------------------------------
Nathan Neulinger                  Univ. of Missouri - Rolla
EMail: nneul@umr.edu                  Computing Services
WWW: http://www.umr.edu/~nneul      SysAdmin: rollanet.org