Ah HA! Found it I think. Go to Monitors under Management in the main
left hand window. Then Edit tab. I suggest changing the Windows Modeler
Cycle Interval first to see what happens (I *think* this is the more
intense). Then if that doesn't help, also the Windows Service Cycle
Interval.
Depending on what happens up to here, the Event Log Cycle Interval might
also be changed...
--
James Pulver
Information Technology Area Supervisor
LEPP Computer Group
Cornell University
shoa wrote:
We increased the server's RAM to 4GB. Zenoss does not appear to be using it and for the time being at least, the total memory used has stayed below the 2GB mark.
The problem continues...
However I think your original idea may fully be valid. I certainly hope for
someone to give me the full directions.
-------------------- m2f --------------------
Read this topic online here:
http://community.zenoss.com/forums/viewtopic.php?p=18591#18591
-------------------- m2f --------------------
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
