Received: (qmail 43494 invoked by uid 501); 19 Dec 2000 12:49:15 -0000
Message-Id: <20001219124915.43493.qmail@locus.apache.org>
Date: 19 Dec 2000 12:49:15 -0000
From: Sanjeev Joshi <schidamb@cisco.com>
Reply-To: schidamb@cisco.com
To: submit@bugz.apache.org
Subject: Multiple apache's getting spwaned
X-Send-Pr-Version: 3.110

>Number:         6994
>Category:       general
>Synopsis:       Multiple apache's getting spwaned
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          mistaken
>Submitter-Id:   apache
>Arrival-Date:   Tue Dec 19 04:50:01 PST 2000
>Closed-Date:    Thu Dec 28 21:27:15 PST 2000
>Last-Modified:  Thu Dec 28 21:27:15 PST 2000
>Originator:     schidamb@cisco.com
>Release:        1.3.6
>Organization:
>Environment:
Windows NT 4.0/98
>Description:
when the Apache is started, I expected that one parent Apache process with  one child starts up. But after some time another parent apache with it's child is 
getting spwaned overwritting the PidFile (httpd.pid). When I kill the Apache,
programmatically, ( using -k shutdown option ) , only that apache process and its child process is getting killed whose pid entry is there in the httpd.pid and hence another apache and its child is hanging out there.
sorry for introduncing Win API , but even if I call  DestroyWindow() from my application, the additional apache is not getting killed ( pl note I can't do TerminateProcess on the pid of additional apache, because there is no way of finding it in Win95 ). 
Pl give the solution to this problem , if u can....
Would'nt it be good if apache was built with some kind of mutex, so that only one instance of apache is running.
>How-To-Repeat:

>Fix:
Would'nt it be good if apache was built with some kind of mutex, so that only one instance of apache is running.
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open-closed
State-Changed-By: wrowe
State-Changed-When: Thu Dec 28 21:27:14 PST 2000
State-Changed-Why:

First, Apache 1.3.6 is horribly dated, please use a more
recent version.

Second, multiple instances of Apache -are- allowed to run
(think in terms of four servers running under different
user accounts with different permissions.)  If you are
trying to kill the Apache NT service, use the SCM.  If you
are trying to kill the Apache 9x service, look at the
service.c code in apache for how apache stops itself.  And
if you are trying to kill console apache, wait for 1.3.15
and post a WM_CLOSE (actually, works in 1.3.14 on NT, but
not under 9x.)

Good luck
 
Class-Changed-From-To: sw-bug-mistaken
Class-Changed-By: wrowe
Class-Changed-When: Thu Dec 28 21:27:14 PST 2000
Severity-Changed-From-To: critical-non-critical
Severity-Changed-By: wrowe
Severity-Changed-When: Thu Dec 28 21:27:14 PST 2000
>Unformatted:
 [In order for any reply to be added to the PR database, you need]
 [to include <apbugs@Apache.Org> 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!     ]