Re: Monit definitely not waiting for stop scripts to complete

[Jason L. Buberel]

Martin, Stanislaw,

Thank you again for your input. With respect to Martin's example 
configuration snippet:

--8<--
  check process tomcat with pidfile /var/run/tomcat.pid
      stop program with timeout 30 seconds = "/etc/init.d/tomcat  
stop" with timeout 1 cycles	# this is default => the timeout option  
not needed
      start program with timeout 30 seconds = "/etc/init.d/tomcat  
start"  with timeout 5 cycles	# after service is started, provide up  
to 5 cycles to start
--8<--

> From this, I conclude that the only way for me to simulate my desired 
> 'synchronous' startup behavior would be to ensure that my start script does NOT 
> create the PID file until the service is fully operational. If needed, I can 
> use 'with timeout N cycles' in order to give the service additional time to 
> completely start. That seems acceptable to me.

Is that syntax already supported in monit 4.10-beta-1?

In regards to the dependency chains and 'hard' vs. 'soft', this sounds like a 
crucial improvement. Stanislaw and I appear to agree strongly with the need for 
a 'hard' dependency link. I would actually suspect that MOST monit users are 
mistakenly assuming that dependency links are treated as 'hard' already:

--8<--
  check process friend with pidfile /var/run/friend.pid
      ...

  check process parent with pidfile /var/run/parent.pid
      ...

  check process child with pidfile /var/run/child.pid
      ...
     depends on parent hard
     depends on friend soft             # this is default
--8<--

Regards,
jason