monit is one of the standard solutions for this sort of thing. I've also used ps-watcher. I would recommend you look at writing a monit script that detects your criteria and kill offending processes.
On Thu, Jan 26, 2012, at 02:29 PM, Rodrick Brown wrote: > Take a look at the preap utility I believe this feature only exists on > 2.6+ kernels > > Sent from my iPhone > > On Jan 26, 2012, at 12:55 PM, David Blank-Edelman <[email protected]> > wrote: > > > Hi- > > We've got a situation where periodically some processes will go rogue on a > > Linux machine, probably after they lose their controlling terminal (i.e. > > someone logs off without quitting the program). We started to hack up > > something that attempts to kill these processes under the "right" > > circumstances (person is logged off the console, is not logged in remotely, > > isn't running it in a screen session, it is taking up a major part of the > > CPU, etc.) but it occurs to me that someone must have written this already. > > It seems like the sort of thing that shared hosting providers must need to > > having running all the time. > > > > Does anyone have a tool they like that they can recommend for this purpose? > > Thanks! > > > > -- dNb > > _______________________________________________ > > Tech mailing list > > [email protected] > > https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech > > This list provided by the League of Professional System Administrators > > http://lopsa.org/ > _______________________________________________ > Tech mailing list > [email protected] > https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech > This list provided by the League of Professional System Administrators > http://lopsa.org/ > -- Philip J. Hollenback [email protected] www.hollenback.net _______________________________________________ Tech mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
