Re: os-windows/6191: When the Apache 'Run' prompt is closed, and the Stop Apache Prompt is ran, the port still remains open with or without the software running. It required a cold-boot or restart to get it to work properly.

[wr...@apache.org]

[In order for any reply to be added to the PR database, you need]
[to include <ap...@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!     ]


Synopsis: When the Apache 'Run' prompt is closed, and the Stop Apache Prompt is ran, the port still remains open with or without the software running.  It required a cold-boot or restart to get it to work properly.

State-Changed-From-To: open-closed
State-Changed-By: wrowe
State-Changed-When: Sun Oct  1 11:27:01 PDT 2000
State-Changed-Why:

You don't state the Apache revision.  Newer versions all
close the child process by killing the pipe to the child
process.  This apparently wasn't happening.  Of course,
if the child has died a horribly violent death but is still
hanging, the results are questionable.

A utility such as sysinternals.com handleex would let you
kill the child process under nearly any conditions.