The following reply was made to PR general/3610; it has been noted by GNATS.
From: Marc Slemko <[EMAIL PROTECTED]> To: Hans de Vreught <[EMAIL PROTECTED]> Cc: Apache bugs database <[EMAIL PROTECTED]> Subject: Re: general/3610: apachectl looks at wrong location pid file Date: Sun, 3 Jan 1999 11:11:40 -0800 (PST) On Sun, 3 Jan 1999, Hans de Vreught wrote: > On Wed, Dec 30, 1998 at 07:50:49PM +0000, [EMAIL PROTECTED] wrote: > > Synopsis: apachectl looks at wrong location pid file > > > > State-Changed-From-To: open-closed > > State-Changed-By: marc > > State-Changed-When: Wed Dec 30 11:50:48 PST 1998 > > State-Changed-Why: > > You need to change the path in the apachectl script if you change > > the location of your PID file. It can't and shouldn't try > > to magically guess what *.conf file to use (after all, if it > > does that then what happens if you change the location of the > > .conf file?). > > But the location of the .conf files is a compile time option, the location of > the PidFile is a run time option. Why can else can you specify the PidFile > at > run time, if the software ignores it and defaults to the compile time? Erm... no. First off, you can put your PidFile directive in any of the config files that you may use. For example, on one system we have shared config files for a dozen or so different servers with different configurations, but the "shared.conf" file contains the PidFile directive, and it is included from the main file. Second, just because there is a compiled in default for the config file doesn't mean that is what is used when someone runs Apache, since they can override it on the command line. There are simply too many places to go wrong trying to magically guess the PID file, especially on systems with multiple copies of Apache running.
