Message-ID: <01e101c35616$859ddad0$0202a8c0@BOB>
From: "Ryan Flowers" <linux@ryanflowers.com>
To: <linux-kernel@vger.kernel.org>
References: <200307292038.h6TKcqlu000338@81-2-122-30.bradfords.org.uk> <20030729134046.A8007@grieg.holmsjoen.com>
Subject: Re: PATCH : LEDs - possibly the most pointless kernel subsystem ever
Date: Tue, 29 Jul 2003 14:15:22 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1170
Lines: 36


> On Tue, Jul 29, 2003 at 09:38:52PM +0100, John Bradford wrote:
> > Ah, I just thought, for debugging purposes we could have LEDs for:
> > 
> > * BKL taken
> > * Servicing interrupt
> > * Kernel stack usage > 2K
> 
> In the way olden days we used the console lights for a realtime
> display of buffer use on a PDP-11.  This type of realtime display
> can be most useful, especially if it's easily configurable.
> 
> -- 
> Randolph Bentson
> bentson@holmsjoen.com
> -
These ideas based on my experience in a production server environment, in
web hosting:

Temperature (Red/Yellow/Green LED)
CPU load (Red/Yellow/Green LED)
Out of Memory (blinking red?)

Don't imagine it would be hard to make a red LED status also set off an
alarm via the PC speaker. Although really a proper system will alert you of
these things anyway, but it would be nice to see it at a glance too.

Ryan Flowers - Reno NV 
http://www.ryanflowers.com

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/