DO NOT REPLY [Bug 10210] New: - 2.0.39 and ZoneAlarmPro 3.0.118 cause locked page state

[bu...@apache.org]

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=10210>.
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=10210

2.0.39 and ZoneAlarmPro 3.0.118 cause locked page state

           Summary: 2.0.39 and ZoneAlarmPro 3.0.118 cause locked page state
           Product: Apache httpd-2.0
           Version: 2.0.39
          Platform: PC
               URL: http://big-baseball.dnsalias.net
        OS/Version: Windows NT/2K
            Status: UNCONFIRMED
          Severity: Critical
          Priority: Other
         Component: Platform
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: daniel.wheeler@big-baseball.com


After uninstalling Apache 1.3.26 and putting a clean install of 2.0.39 on my server, server (Win2000 SP2 with all M$ support patches) would blue screen with a "process has locked pages" error within 10 minutes of system start (happened total of four times, each time was within 9-10 minutes, precisely).  After several reboots and bouts of swearing later, I discovered that if I did not start my firewall, ZoneAlarm Pro 3.0.118 (installed and working fine for 3 months), there would be no blue screen.  To make sure I ran system without Apache started and ZoneAlarm running and there were no crashes, when Apache started blue screen would come back within the 9-10 minute range.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org