On 10 May 2013, William A. Rowe, Jr. wrote:
On Wed, 08 May 2013 19:08:56 -0500 Daniel Ruggeri drugg...@primary.net
wrote:
On 5/8/2013 3:29 PM, Rainer Jung wrote:
Careful: I didn't test it but we delete the pid file during web server
shutdown. That might remove /dev/null then.
On a
On Wed, 08 May 2013 19:08:56 -0500
Daniel Ruggeri drugg...@primary.net wrote:
On 5/8/2013 3:29 PM, Rainer Jung wrote:
Careful: I didn't test it but we delete the pid file during web
server shutdown. That might remove /dev/null then.
On a quick look through the code I had the impression
On Mon, 6 May 2013 23:42:27 +0100
Tom Jones t...@inpher.com wrote:
We use process supervision and don't have a use for pid files. We
are running multiple httpd instances, and have the config management
to create a writable configured place for each instance to put its
pid file.
Surely you
On 08.05.2013 20:06, William A. Rowe Jr. wrote:
On Mon, 6 May 2013 23:42:27 +0100
Tom Jones t...@inpher.com wrote:
We use process supervision and don't have a use for pid files. We
are running multiple httpd instances, and have the config management
to create a writable configured place
On 5/8/2013 3:29 PM, Rainer Jung wrote:
Careful: I didn't test it but we delete the pid file during web server
shutdown. That might remove /dev/null then.
On a quick look through the code I had the impression you can not easily
get rid of the pid file.
Agreed - setting to /dev/null under the
We use process supervision and don't have a use for pid files. We
are running multiple httpd instances, and have the config management
to create a writable configured place for each instance to put its
pid file.
This config management has some ongoing cost to maintain, and we would
find it nicer
