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 ------- Additional Comments From [EMAIL PROTECTED] 2003-12-18 12:33 ------- >Does this mean that there is only a single pipe shared between the parent >and all children? yes >For example, could it happen that the data sent through >the pipe gets "stuck" and returned to each child on a read? (I'm asking >because this seems to be a platform-specific problem on OpenBSD - >perhaps OpenBSD behaves differently or is simply bugged?) If that happens, it is {dependence-on-nonportable-behavior|OpenBSD-bug} (your choice). All I can say is that nobody else has reported this. Make sure thread support didn't get enabled in APR (check APR_HAS_THREADS in apr.h) whenever there is screwy behavior in Apache 2 on a *BSD system. Here's how to check: Trace the parent process to see if it wrote one '!' character (intending to terminate one extra child process) or if it wrote multiple. If it wrote one but multiple children were able to read the character, there is some sort of race condition in OpenBSD kernel and this should be taken up with the OpenBSD experts. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
