Alter RHEL3 low memory countermeasures? lars at
Wed Jul 6 14:30:07 CDT 2005

Hi David,

Maybe this is not what you asked for... I would use nagios to monitor
your server. When the load/memory usage/whatever gets to high nagios can
execute a script (or anything else) on your server by ssh for example
that kills the offending program.

This usualy works great. If you put your monitoring threashold on a
reasonable level you/nagios should be able to fix the problem before it
crashes the server.

Another good thing as you mention (try the other way arount, give you
memory hungry processes niced to a positive number and let other
processes have their normal prio).  Since sshd draws no cpu/memory to
speak of compared to your cpu-and-memory hungry programs will still have
access to allmost the same amount of cpu-time.


On Wed, 6 Jul 2005, David Hubbard wrote:
> If that's not possible, my next thought was to
> have in inittab, an instance of the tcpserver
> program (a tcp listener that invokes a program given
> as an argument to it when connected to) with the
> arguments to call /usr/bin/killall -9 badprogram
> when accessed.  I could have it listen on a firewalled
> unused low port and be niced to a negative number.
> That way if the server is overloaded and in the process
> of dying, I could just "telnet badserver 12" from 
> somewhere else and hopefully the high priority of this
> process would allow it to sneak in and run and fix
> the problem without needing to power cycle the server.

More information about the Linux-PowerEdge mailing list