Received: (qmail 11492 invoked by uid 2012); 30 Dec 1998 10:59:20 -0000 Message-Id: <19981230105920.11491.qmail@hyperreal.org> Date: 30 Dec 1998 10:59:20 -0000 From: Hans de Vreught Reply-To: J.P.M.deVreught@cs.tudelft.nl To: apbugs@hyperreal.org Subject: apachectl looks at wrong location pid file X-Send-Pr-Version: 3.2 >Number: 3610 >Category: general >Synopsis: apachectl looks at wrong location pid file >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: closed >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Wed Dec 30 05:10:00 PST 1998 >Last-Modified: Sun Jan 3 11:20:00 PST 1999 >Originator: J.P.M.deVreught@cs.tudelft.nl >Organization: >Release: 1.3.3 >Environment: uname -a -> SunOS chrysler 5.5 Generic_103093-10 sun4u sparc gcc --version -> 2.8.1 >Description: Although in httpd.conf you supply the place of the PidFile, the script apachectl doesn't use that location at all. So, if you have supplied a different PidFile location, apachectl complains that it can't find the PidFile. >How-To-Repeat: Simply change the location of the PidFile in httpd.conf and do "apachectl stop" and "apachectl restart" or "apachectl graceful". >Fix: Well, roughly. You could do a grep on httpd.conf in the apachectl script to catch the location of the PidFile. But then the problem is to find out where the httpd.conf will be located after installation. Shouldn't be that hard to change the script a little bit during installation to incorporate the location of httpd.conf. >Audit-Trail: 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?). From: Marc Slemko To: Hans de Vreught Cc: Apache bugs database 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, marc@apache.org 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. >Unformatted: [In order for any reply to be added to the PR database, ] [you need to include in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [automatically because of the potential for mail loops. ] [If you do not include this Cc, your reply may be ig- ] [nored unless you are responding to an explicit request ] [from a developer. ] [Reply only with text; DO NOT SEND ATTACHMENTS! ]