ack sent
Forwarded message:
> From hqm@ua.com Tue Oct 3 14:44:41 1995
> Date: Tue, 3 Oct 1995 14:46:09 -0700
> Message-Id: <199510032146.OAA19608@nexus.datawave.net>
> From: Henry Minsky <hqm@ua.com>
> To: apache-bugs@apache.org
> Subject: suggestion for restarting server on the fly
>
>
> I wanted to suggest that you adopt a mechanism which the CERN httpd
> server has for restarting it, which does not involve the user having
> to grovel around for the file containing the pid of the process:
>
> With CERN you can just do:
>
> /usr/local/bin/httpd -restart
>
> I.e., if the -restart arg is passed to a new instance of the program,
> the new process just reads its existing pid file and sends the
> appropriate restart signal to the old process, and then dies.
>
> This way ,the user does not need to know where the pidfile lives, they
> simply need to remember, at most where, the server config directory is.
> i.e,
>
> /usr/local/bin/httpd -r /path/to/config_dir -restart
>
Forwarded message:
> From hqm@ua.com Tue Oct 3 14:44:41 1995
> Date: Tue, 3 Oct 1995 14:46:09 -0700
> Message-Id: <199510032146.OAA19608@nexus.datawave.net>
> From: Henry Minsky <hqm@ua.com>
> To: apache-bugs@apache.org
> Subject: suggestion for restarting server on the fly
>
>
> I wanted to suggest that you adopt a mechanism which the CERN httpd
> server has for restarting it, which does not involve the user having
> to grovel around for the file containing the pid of the process:
>
> With CERN you can just do:
>
> /usr/local/bin/httpd -restart
>
> I.e., if the -restart arg is passed to a new instance of the program,
> the new process just reads its existing pid file and sends the
> appropriate restart signal to the old process, and then dies.
>
> This way ,the user does not need to know where the pidfile lives, they
> simply need to remember, at most where, the server config directory is.
> i.e,
>
> /usr/local/bin/httpd -r /path/to/config_dir -restart
>