Re: [monit] Monitor process that is not allways running

[Jan-Henrik Haukeland]

On 4. des.. 2008, at 15.57, Ismo Tanskanen wrote:

> Now, I have noticed that I have one problematic process,  
> Mythtranscode, what sometimes starts use a huge amount of memory,  
> what causes system to come extra slow. Problem is, that  
> mythtranscode is not allways running, only when mythbackend calls it.
>
> What I want to do, is just check if process is running, and if it is  
> eating a lot of memory, then kill it.

Is mythtranscode started by mythbackend? If so and as a hack you can  
test mythbackend like so:

if totalmemory > X MB then exec "/script/to/mythtranscode stop"

Total memory include the current process (mythbackend) and its  
children (mythtranscode).