good console bases sys monitors

[aaron d]

iftop, iostat,  vmstat, free, df ? they aren't monitors in the sense that
you are talking in the second half of your question (i.e. they don't take
action, they simply tell you what is going on). In my experience with
monitoring systems, you generally would not want something just killing off
random PIDs at it's own discretion, let alone REBOOTING because of a memory
leak. We never reboot :) Usually you would want to receive some form of
alert so that you can use these tools to investigate the issue and possibly
take steps to keep it from happening over and over again. However there may
be a time when you just want to kill a notoriously bad process (google
chrome anyone?) if it gets out of hand.

conky (http://conky.sourceforge.net/) is not a console-based monitor, but is
very nice, and of course if you are monitoring remotely you could always
forward X to your local machine.

-aaron

On Sat, Jul 31, 2010 at 6:01 PM, Rajinder Yadav <devguy.ca-Re5JQEeQqe8AvxtiuMwx3w at public.gmane.org> wrote:

> Other than top, that's as far as my linux-fu gets me =P, what other console
> based monitors are you guys using that has low cpu load for things like:
>
> network activity, file activity, storage space, low memory
>
> if the system is overloaded, i'm memory leaks, errant process is there a
> monitor that will force the server to reboot? i am asking more for an
> education purpose and not any kind of immediate use
>
> Thanks,
> Rajinder
> --
> The Toronto Linux Users Group.      Meetings: http://gtalug.org/
> TLUG requests: Linux topics, No HTML, wrap text below 80 columns
> How to UNSUBSCRIBE: http://gtalug.org/wiki/Mailing_lists
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gtalug.org/pipermail/legacy/attachments/20100801/041cad88/attachment.html>