> > I was too until someone brought up the lack of processor utilization
> > reporting in ComOS, meaning there is no way to determine how hard you are
> > hitting your CPU. Take a couple of full views, and do some filtering;
>
> I love the whole concept of CPU usage reporting. It's a perfect
> example of Heisenberg's Uncertainty Principle. How much CPU was being
> used before the CPU usage monitor was run? Who knows? It changes the
> condition of the CPU by observing the CPU's condition.
Personally, I feel much safer adding the overhead of a CPU usage reporting
utility and knowing that I am *not* at the limit of what a given box can
do with the reporting enabled. What is option #2? Waiting until I
experience some sort of problem and just guessing, running the risk of
negatively affecting the stability of a network, and possibly wasting time
exhausting other possibilities until I find the source of the problem.
Option #2(the current Livingston option) stinks(but I still like you guys
for most everything else....)
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
Patrick Greenwell (510) 934-2153 voice
Network Administrator (510) 906-1173 fax
European Telecom
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/