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=7932>. 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=7932 BSoD Attemping to Terminate Apache with ZoneAlarm Installed [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | ------- Additional Comments From [EMAIL PROTECTED] 2002-09-24 15:20 ------- With all due respect folks, the solution that users like myself have found is to bail on Apache2 and revert to 1.3. I've seen no other conflicts between ZoneAlarm and other applications, including NetMeeting, which I use frequently. This is not just an inconvenience with Apache2. It does not merely BSOD when you attempt to stop the Apache2 service. Long before that, Apache2 silently ceases to operate, apparently whenever it hits a threshold requiring that it spawn another child or has used a certain number of threads. Tinkering with those settings alters the length of time until failure. The BSOD occurs *after* functionality already has been lost due to this failure. Meanwhile, objecting to ZoneAlarm is like objecting to MacAfee or Norton. In many environments, it isn't a choice whether the user will install it. It is mandated by institutional policies. If Apache2 can't work with it, Apache2 is the one to go. I understand the difficulty in debugging closed source vs. open source. But I honestly believe it's in Apache's interest to work more closely with ZoneAlarm on this one. Otherwise, at least within the low-volume server community, it's Apache, not ZoneAlarm, who's going to get a black eye among users. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
