>Number: 5281 >Category: general >Synopsis: Proposal for pid file naming, which enables multiple apache >instances >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: open >Class: change-request >Submitter-Id: apache >Arrival-Date: Wed Nov 10 05:30:01 PST 1999 >Last-Modified: >Originator: [EMAIL PROTECTED] >Organization: apache >Release: 1.3.6 >Environment: SunOS laborant 5.7 Generic sun4u sparc SUNW,Ultra-5_10 gcc 2.95 GNU-binutils-2.9.1 Although the problem is probably not dependent on any of these >Description: in a non-root working environment, where more than one user may be willing to run a private instance of apache on one machine, the current default pid file naming leads to clashes. >How-To-Repeat: On one and the same machine start two instances of apache $ httpd -f <httpd:8000.conf> $ httpd -f <httpd:8001.conf> , where both config files contain the line with the ``PidFile'' directive unchange from the default.
You will experience, that one apache instance overwrites the PidFile of the other instance /*last one wins*/. >Fix: I suggest to replace the PidFile directive in httpd.conf by the [new] default # PidFile: The file the server for Port 80 should log its pid to PidFile /var/run/httpd:80.pid . I think, this would give thinking of any non-root apache configurer the right direction. Since for every machine, there cannot be more than one webserver instance per port, this naming scheme should be unique. >Audit-Trail: >Unformatted: [In order for any reply to be added to the PR database, you need] [to include <[EMAIL PROTECTED]> in the Cc line and make sure the] [subject line starts with the report component and number, with ] [or without any 'Re:' prefixes (such as "general/1098:" or ] ["Re: general/1098:"). If the subject doesn't match this ] [pattern, your message will be misfiled and ignored. The ] ["apbugs" address is not added to the Cc line of messages from ] [the database 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! ]
