[In order for any reply to be added to the PR database, ] [you need to include <[EMAIL PROTECTED]> 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! ]
Synopsis: Proposal for pid file naming, which enables multiple apache instances State-Changed-From-To: open-closed State-Changed-By: marc State-Changed-When: Wed Nov 10 08:10:43 PST 1999 State-Changed-Why: There certainly can be more than one PID file per port and, on many machines, there is. I really don't see that it is necessary to change the default PID file. It would add considerable confusion for people running one server that listens to multiple ports and wouldn't really solve the problem that you describe, since people can have web servers using the same port on different IPs. I don't think it is unreasonable to simply expect peple to be able to configure each instance of their webserver to what whatever unique files are necessary.
