<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://www.eiffelroom.com" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>eiffelroom - daemon - Comments</title>
 <link>http://www.eiffelroom.com/tag/daemon</link>
 <description>Comments for &quot;daemon&quot;</description>
 <language>en</language>
<item>
 <title>Ok.  I would have thought</title>
 <link>http://www.eiffelroom.com/article/daemon_howto#comment-199</link>
 <description>&lt;p&gt;Ok.  I would have thought that when detach returned, after the call to fork, that execution would have continued within the if-then, and then fallen through bypassing the call to execute.  I was confused, I guess, so I&#039;ll have to study it some more.&lt;/p&gt;

</description>
 <pubDate>Mon, 16 Apr 2007 06:28:33 -0700</pubDate>
 <dc:creator>Neitsdelf</dc:creator>
 <guid isPermaLink="false">comment 199 at http://www.eiffelroom.com</guid>
</item>
<item>
 <title>No. Detach, forks and then</title>
 <link>http://www.eiffelroom.com/article/daemon_howto#comment-196</link>
 <description>&lt;p&gt;No. Detach, forks and then calls execute in the new process.&lt;/p&gt;

</description>
 <pubDate>Sun, 15 Apr 2007 23:46:34 -0700</pubDate>
 <dc:creator>patrickr</dc:creator>
 <guid isPermaLink="false">comment 196 at http://www.eiffelroom.com</guid>
</item>
<item>
 <title>Correction?</title>
 <link>http://www.eiffelroom.com/article/daemon_howto#comment-192</link>
 <description>&lt;p&gt;Shouldn&#039;t the call to &amp;quot;execute&amp;quot; be outside of the if-then conditional?&lt;/p&gt;

</description>
 <pubDate>Fri, 13 Apr 2007 07:13:56 -0700</pubDate>
 <dc:creator>Neitsdelf</dc:creator>
 <guid isPermaLink="false">comment 192 at http://www.eiffelroom.com</guid>
</item>
<item>
 <title>Eiffel and Unix</title>
 <link>http://www.eiffelroom.com/blog/patrickr/of_daemons_and_threads#comment-185</link>
 <description>&lt;p&gt;I personally would be interested to know how to setup signal handlers in Eiffel.&lt;/p&gt;

</description>
 <pubDate>Mon, 02 Apr 2007 15:40:24 -0700</pubDate>
 <dc:creator>mtn</dc:creator>
 <guid isPermaLink="false">comment 185 at http://www.eiffelroom.com</guid>
</item>
<item>
 <title>That&#039;s basically not that</title>
 <link>http://www.eiffelroom.com/blog/patrickr/of_daemons_and_threads#comment-184</link>
 <description>&lt;p&gt;That&#039;s basically not that hard. In general on Unix/Linux, the way it is done is to let the process fork itself and then end the parent process. As soon as the parent process exits, the child process is automatically inherited by the init process and can therefore be considered a daemon. In Eiffel probably the easiest way to do it, is to use eposix. Another aspect that should also be done is to implement some signal handlers (e.g. for the TERM signal, to be able to shut down a daemon), I also did this using eposix. If there&#039;s interest I can write a quick article about it.&lt;/p&gt;

</description>
 <pubDate>Mon, 02 Apr 2007 15:33:05 -0700</pubDate>
 <dc:creator>patrickr</dc:creator>
 <guid isPermaLink="false">comment 184 at http://www.eiffelroom.com</guid>
</item>
<item>
 <title>How do you turn your processes into daemons?</title>
 <link>http://www.eiffelroom.com/blog/patrickr/of_daemons_and_threads#comment-183</link>
 <description>&lt;p&gt;Would be interesting to know.&lt;/p&gt;

</description>
 <pubDate>Mon, 02 Apr 2007 15:21:43 -0700</pubDate>
 <dc:creator>mtn</dc:creator>
 <guid isPermaLink="false">comment 183 at http://www.eiffelroom.com</guid>
</item>
</channel>
</rss>
