----- Original Message ----- > From: "Andy Brezinsky via Outages" <outages@outages.org>
> If you see the issue again, get on the unit and run 'diag sys top' to > find the process that is burning CPU. We have in the past seen ssl imd > (instant messaging intercept daemon), cache etc cause issues. That will > at least point you in the right direction to what is causing issues. I had; the first time it was ipsmonitor or ipsengine (I forget which); the second and subsequent times, it was scanunitd. Both times, it settled down *just* before support got me off hold; it was slightly maddening. Cheers, -- jra -- Jay R. Ashworth Baylink j...@baylink.com Designer The Things I Think RFC 2100 Ashworth & Associates http://www.bcp38.info 2000 Land Rover DII St Petersburg FL USA BCP38: Ask For It By Name! +1 727 647 1274 _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages