We have had problems on Solaris 2.7 FW ver 4.0 SP0 and 4.1 SP0 using the
connect control module with a fw process called in.pingd. The process
consumes memory and cpu to 100% utilization of resources, then dies and
restarts.
The problem is reported to be fixed in 4.1 SP2. Has anyone had any
problems with in.pingd or any other runaway processes in V4.1 SP3?
Thanks
================================================================================
To unsubscribe from this mailing list, please see the instructions at
http://www.checkpoint.com/services/mailing.html
================================================================================
