<br><br>
<div><span class="gmail_quote">On 22/01/07, <b class="gmail_sendername">Dave Ansell</b> <<a href="mailto:dave@theansells.com">dave@theansells.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><br> My only issue is that the backend service occasionally dies for no<br>aparent reason. This has been the case in every incarnation to date,
<br>whatever I try. It doesnt happen often, but enought to be annoying and<br>reduce WAF etc.<br><br> I guess this behaviour is to be expected with any developing software.<br>However it strikes me that it would be relatively simple to set up an
<br>independant process to monitor the status of the backend and kick it back<br>into life automatically if it dies. (ie what I do now manually!)</blockquote>
<div> </div>
<div>Several people (including me) use Daemontools (sorry, I don't have a URL handy, check the archives) to accomplish this. The documentation is not particuarly good, but once you get that figured out it's fairly straightforward to get working.
</div>
<div> </div>
<div>It won't handle cases of the backend hanging (which occurs from time to time), but it does quite nicely handle cases where the backend crashes.</div>
<div><br>-- <br>aaron<br><br>"Oh oh oh. I'm incoherent with excitement. Please tell me what fascinating<br>bit of badger-spewtumly inconsequential trivia you will assail me with next."<br> -- Arthur Dent
</div></div>