You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2003/05/28 22:11:39 UTC
DO NOT REPLY [Bug 14987] -
Not able to kill the process initated from cgi
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14987>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14987
Not able to kill the process initated from cgi
wrowe@apache.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WORKSFORME
------- Additional Comments From wrowe@apache.org 2003-05-28 20:11 -------
This would be a perl issue. You always have permission to terminate any
process you create, *if* you retain the handle to the process. Apparently
perl is trying to obtain a new handle to this process.
Apache has certain security/privilage settings to prevent abuse, etc, and
I'm afraid you will need to look into how to use the perl win32:: createprocess
API to invoke your exe and therefore be able to terminate it. You also may
have problems with stdin/out handles being inherited yet again by the child
process which you may have to address in order to terminate the child.
In any case, this isn't a flaw within the Apache server, and 1.3 is no longer
heavily supported on Win32. You would be better served moving to 2.0 where
more active developers may be able to help.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org