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=21645>. 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=21645 Child processes die after each request ( after connection is closed) on OpenBSD Summary: Child processes die after each request ( after connection is closed) on OpenBSD Product: Apache httpd-2.0 Version: 2.0.47 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: Other Component: Core AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] I'm running 2.0.47 on OpenBSD, prefork. The following problem exists: After Apache is running for some time, could be minutes or hours, every child process exits after the request has been served. Meaning: client connects, a free httpd takes the connection, the client closes, the httpd that served the request exits, a new one is spawned instead. MaxRequestPerChild is set to 0. The relevant section looks like this: <IfModule prefork.c> StartServers 5 MinSpareServers 5 MaxSpareServers 10 MaxClients 100 MaxRequestsPerChild 0 </IfModule> This behaviour only starts after some uptime of httpd and puts unnecessary load on the server, because many children are killed and spawned again for every request. In the server status it looks like this: Slot 1-4 serves a request (if browser uses keepalive more than 1 request gets served) 1-4 12441 0/0/162 W Connection closes, child pid 12441 has exited 1-4 - 0/0/170 . This problem seems to be specific with OpenBSD and also existed with 2.0.46 which was the first version we tested. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
