<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
i know some of those tools, not an avid user of them, will read up.<br>
<br>
as for rebooting or restarting errant process, i was thinking of this
in terms of my own web-server hosting setup, in particular my own rails
apps, since i would be logging error, i would know what was causing any
kind of abnormal memory, cpu, network load, it would be a stop gap
solution till the real issue was rectified in the code or through load
balancing, etc.<br>
<br>
i heard a talk from the reddit founder talking about fail often, crash
early and they were using some of this monitoring techniques, it was
interesting and something to mull over for sure =)<br>
<br>
thanks,<br>
Rajinder<br>
<br>
<br>
<br>
On 10-08-01 08:19 AM, aaron d wrote:
<blockquote
cite="mid:AANLkTik8jfqh89Ocms+pFvUY9YJsNqOD5fyvxak9i2pH-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org"
type="cite">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.
<div>
<div><br>
</div>
<div>conky (<a moz-do-not-send="true"
href="http://conky.sourceforge.net/">http://conky.sourceforge.net/</a>) 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.</div>
<div><br>
</div>
<div>-aaron</div>
<div><br>
</div>
<div>
<div class="gmail_quote">On Sat, Jul 31, 2010 at 6:01 PM, Rajinder
Yadav <span dir="ltr"><<a moz-do-not-send="true"
href="http://devguy.ca">devguy.ca</a>@<a moz-do-not-send="true"
href="http://gmail.com">gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">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:<br>
<br>
network activity, file activity, storage space, low memory<br>
<br>
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<br>
<br>
Thanks,<br>
Rajinder<br>
<font color="#888888">--<br>
The Toronto Linux Users Group. Meetings: <a moz-do-not-send="true"
href="http://gtalug.org/" target="_blank">http://gtalug.org/</a><br>
TLUG requests: Linux topics, No HTML, wrap text below 80 columns<br>
How to UNSUBSCRIBE: <a moz-do-not-send="true"
href="http://gtalug.org/wiki/Mailing_lists" target="_blank">http://gtalug.org/wiki/Mailing_lists</a><br>
</font></blockquote>
</div>
<br>
</div>
</div>
</blockquote>
<br>
</body>
</html>