Monit dependancies and expected behaviour

[Chris McKenzie]

Hi everyone.

I've built a bit of a web interface for monit into another CGI application 
to dyamically list monitored processes and whether they're running, stopped 
or starting. It all works great, but I did notice some specific process 
stopping behaviour when the stopped process is another process dependancy.

I'm using Monit 4.5.1 for Linux (RedHat Enterprise 3.0), with the following 
process control entires, after I stop proc2 using "monit proc2 stop", the 
next monit poll will bring proc2 back up.

check process proc1
  with pidfile /var/run/proc1.pid
  start program = "/etc/init.d/proc1 start"
  stop program = "/etc/init.d/proc1 stop"
  depends on proc2

check process proc2
  with pidfile /var/run/proc2.pid
  start program = "/etc/init.d/proc2 start"
  stop program = "/etc/init.d/proc2 stop"

I haven't completely tested the reverse out to decide if this dependant 
stopping behaviour is expected. I mean I believe I've seen monit start 
processes in the correct order if dependancies are present, or if monit 
finds proc2 down, it will bring proc2 up and restart proc1. (in the right, 
dependant, order)

It just confusing from the perspective of the web interface. One second a 
process is legitimately stopped (using monit stop), and the next check 
(using monit status) finds proc2 running again.

Any ideas or confirmation? Thanks!

- Chris