<tt><font size=2>> This should work exactly as you've written it.</font></tt>
<br>
<br><tt><font size=2>I believe I figured out my problem. A line in the
watchdog conf file had</font></tt>
<br><tt><font size=2>accidently become uncommented, and thus I had 2 "stop
on" stanzas.</font></tt>
<br><tt><font size=2>Looks like the last one wins. :-)</font></tt>
<br>
<br><tt><font size=2>It's working now.</font></tt>
<br><tt><font size=2><br>
> > What would be nice is a "restart on ..." stanza. I
could also see that<br>
> > an "restart limit ..." stanza should follow. <br>
> > <br>
> We had something like this once; it got removed when the states were<br>
> simplified such that a restart was roughly equivalent to stop/start.
If<br>
> it came back, you'd then have to have additional events for restarting<br>
> and restarted.</font></tt>
<br>
<br><tt><font size=2>I'm getting the behavior that I want. When I do an
"initctl restart application"</font></tt>
<br><tt><font size=2>it stops the watchdog, stops the application, starts
the application, starts</font></tt>
<br><tt><font size=2>the watchdog. To get this behavior, I need to do an
"initctl restart ..."</font></tt>
<br><tt><font size=2>instead of "initctl emit ...", which isn't
a big deal.</font></tt>
<br><tt><font size=2><br>
On a more general note, I have to say that a policy-based event-driven
</font></tt>
<br><tt><font size=2>service manager is very elegant. Nice job.</font></tt>
<br>
<br><tt><font size=2>-- Marcel</font></tt>