<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hey<div><br class="webkit-block-placeholder"></div><div>Is the "spawn-fcgi" the one that is built with Lighttpd? If so, add the "-n" flag so that it won't fork to the background. I "spawn-fcgi" to handle PHP built as a FastCGI application.</div><div><br class="webkit-block-placeholder"></div><div>Mike</div><div><br><div><div>On 31 Jan 2008, at 02:20, <a href="mailto:mobiledreamers@gmail.com">mobiledreamers@gmail.com</a> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">it is not working with spawn-fcgi<br>since spawnfcgi spawns a child <br>and exits<br>so supervise keeps trying to spawn childs<br>continuously<br><br><span style="font-weight: bold;">service/run</span><br>#!/bin/sh<br>cd /home/mark/work/code<br> <br>exec /opt/local/bin/spawn-fcgi &nbsp; -f /home/mark/work/code/code.py -p 9500&nbsp; &gt; /tmp/restart.log 2&gt;&amp;1 &amp;<br>exec cat /tmp/restart.log &amp;<br>exec /opt/local/bin/spawn-fcgi &nbsp; -f /home/mark/work/code/code.py -p 9501&nbsp; &gt; /tmp/restart.log 2&gt;&amp;1 &amp; <br> exec cat /tmp/restart.log &amp;<br><br>exec /opt/local/bin/spawn-fcgi&nbsp; -f /home/mark/work/code/code.py -p 9502&nbsp; &gt; /tmp/restart.log 2&gt;&amp;1 &amp;<br>exec cat /tmp/restart.log &amp;<br><br>exec /opt/local/bin/spawn-fcgi -f /home/mark/work/code/code.py -p 9503 &gt; /tmp/restart.log 2&gt;&amp;1 ^<br> exec cat /tmp/restart.log &amp;<br>~<br><br>Starting the backends<br><span style="font-weight: bold;">supervise service</span><br><br>Error <br>it keeps trying to restart the backends since <br><div><span class="gmail_quote">On 1/30/08, <b class="gmail_sendername"><a href="mailto:mobiledreamers@gmail.com">mobiledreamers@gmail.com</a></b> &lt;<a href="mailto:mobiledreamers@gmail.com">mobiledreamers@gmail.com</a>&gt; wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <a href="http://www.google.com/search?hl=en&amp;client=mozilla&amp;rls=org.mozilla%3Aen-US%3Aunofficial&amp;q=daemontools-nginx&amp;btnG=Search" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://www.google.com/search?hl=en&amp;client=mozilla&amp;rls=org.mozilla%3Aen-US%3Aunofficial&amp;q=daemontools-nginx&amp;btnG=Search</a><br> incidentally what is daemontools-nginx then?<div><span class="e" id="q_117cd2e30befb82a_1"><br><br><div><span class="gmail_quote">On 1/30/08, <b class="gmail_sendername"><a href="mailto:mobiledreamers@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">mobiledreamers@gmail.com</a></b> &lt;<a href="mailto:mobiledreamers@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">mobiledreamers@gmail.com</a>&gt; wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Thanks cliff so the best practises for python backends is daemontools supervise?<br>thanks a lot<div><span><br><br><div class="gmail_quote">On Jan 30, 2008 4:03 PM, Cliff Wells &lt;<a href="mailto:cliff@develix.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">cliff@develix.com</a>&gt; wrote:<br> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><br>On Wed, 2008-01-30 at 15:55 -0800, <a href="mailto:mobiledreamers@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">mobiledreamers@gmail.com</a> wrote:<br> &gt; Running nginx with daemontools<br>&gt; Hey guys I m trying to figure out how to run nginx and the backends<br>&gt; using supervise in daemon mode<br>&gt; the idea is to run the fastcgi backends in supervise daemonzied mode<br> &gt; so that if they get killed due to memory leaks or overload or whatever<br>&gt; error they can be rebooted by supevise automatically wtihout human<br>&gt; intervention<br>&gt; thanks for sharing ideas<br><br></div>I think the best idea is to *not* run Nginx under daemontools. &nbsp;But by<br> all means run your FCGI processes under it since Nginx won't<br>automatically restart them if they die.<br><br>Regards,<br><font color="#888888">Cliff<br><br><br><br></font></blockquote></div><br> </span></div></blockquote></div><br> </span></div></blockquote></div><br></blockquote></div><br></div></body></html>