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 Unable to Terminate when ZoneAlarm Installed ------- Additional Comments From [EMAIL PROTECTED] 2002-04-21 20:01 ------- Ahhh, no offense, Joshua, but that is just plain sillyness. You are joking, right? So if there is a conflict between Apache software and another vendor, just blame the other vendor and call it a day? Here are the reasons why that statement makes no sense whatsoever: 1. Apache 1.3.xx works just fine with Zone Alarm even if Zone Alarm is, supposedly, "messing up the windows sockets interface". If so, why does Apache work just fine and Apache2 doesn't? 2. There are reasons why I have Zone Alarm installed in the first place so telling me to just "remove Zone Alarm" in order to run Apache2 is just plain Arrogant. Basically you are saying that your software is more important than other software. I'll just move back to Apache 1.3.24 to, temporarily, solve the issue; not uninstall a program that performs an important function on my networked machine. 3. Lots of other software seems to run just fine with Zone Alarm including other types of servers (Apache 1.2.34, Serv-u FTP, Tomcat 3.3.1/4.1-dev, etc...) 4. Zone Alarm could simply be exposing a subtle flaw in Apache2 which is something you seem unwilling to consider. Maybe it is the other way around? Who knows? Either way, the issue certainly deserves more investigation than you seem think is worthwhile. Please let me know if my statements are totally invalid and, if so, provide your reasoning. I think they are quite reasonable and it would certainly put Apache2 in a better light if it worked with pretty much *the* most popular personal firewall on Windows. I love open source and I think Apache does a tremendous job developing open source software, but it irks me when open source developers just blow off valid issues like this. There is an issue and there is a chance it might be a bug in Apache2. If so, the solution is to fix Apache2. If not, the solution is to alert Zone Alarm that (and, ideally, how) they are breaking a Apache2 so they can get things working properly on their end. Either way, Apache2 users benefit and everyone is happy. Jake
