On Sun, 2007-09-16 at 15:59 +0200, Tino Schwarze wrote: > I'm still struggling with the "only 1% idle" problem on some servers. > IMO it's not a bad thing to have 0% idle. You're right, it's an indicator of possible problems, but there are plenty of use cases where 0% idle (even over some extended time period) isn't something alarming. I use it often together with *.cpu delay=30 in bb_event_generator.cfg, since on most systems high load and/or high CPU usage indicate a problem if they persist for a long time. > localhost(kenny) idle_red=0 load This is nearly fine. Only that uxmon is falling back to idle_red=10 if idle_red is not set ... and 0 is considered "not set" (argh). Probably, idle_red=-1 will do the trick. > Is there a way to look for load instead of idle? The cpuload test checks the load average. So if you feel unhappy with "load", either drop it completely (you are not forced to use it :-)) or if you still want to get graphs try setting the limits to -1 as suggested above. The cpuload test is independent of the load test (it's the one reporting "CPU load = 2.21" in your example output). BTW: it's arguments are cpu_yellow and cpu_red for specifying the load average at which yellow/ red should be reported. Best regards, Tom -- ---------------------------------------------------------------------------- Thomas Aeby, Kirchweg 52, 1735 Giffers, Switzerland, Tel: (+41)264180040 Internet: suppressed PGP public key available ---------------------------------------------------------------------------- ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Bigsister-general mailing list suppressed https://lists.sourceforge.net/lists/listinfo/bigsister-general
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.