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 2005/11/11 12:38:41 UTC
DO NOT REPLY [Bug 37467] New: -
Apache does not terminate suexec CGI processes when connection closed
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=37467>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=37467
Summary: Apache does not terminate suexec CGI processes when
connection closed
Product: Apache httpd-2.0
Version: 2.0.54
Platform: Sun
OS/Version: Solaris
Status: NEW
Severity: normal
Priority: P2
Component: mod_suexec
AssignedTo: bugs@httpd.apache.org
ReportedBy: keturner@livejournal.com
we have a CGI process which runs forever, terminating when the user closes the
session (e.g. closes their browser window).
normally, this works fine. however, when run as an suexec CGI, the process
never exits, because Apache cannot kill it.
from dtrace, with a normal CGI:
CPU ID FUNCTION:NAME
0 37018 kill:entry pid = 25355
0 37019 kill:return ret = 0
0 37018 kill:entry pid = 25355
0 37019 kill:return ret = 0
with the suexec CGI:
1 37018 kill:entry pid = 25404
1 37019 kill:return ret = -1
1 37018 kill:entry pid = 25404
1 37019 kill:return ret = -1
the correct fix is for the CGI script to notice write errors and exit; however,
it would be nice if Apache or suexec learnt how to kill its setuid children.
(Observed on Solaris 10 AMD64, worker MPM.)
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org