<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
<title>Snipplr</title>
<link>http://snipplr.com/language/c-plus-plus/tags/fork</link>
<description>Recent snippets posted on Snipplr.com</description>
<language>en-us</language>
<pubDate>Fri, 05 Sep 2008 01:54:04 GMT</pubDate>
<item>
<title>(C++) racing condition - Feb30th1712</title>
<link>http://snipplr.com/view/4509/racing-condition/</link>
<description><![CDATA[ <p></p> ]]></description>
<pubDate>Sun, 13 Jan 2008 08:50:56 GMT</pubDate>
<guid>http://snipplr.com/view/4509/racing-condition/</guid>
</item>
<item>
<title>(C++) Safe application spawning with fork+exec - CUViper</title>
<link>http://snipplr.com/view/1790/safe-application-spawning-with-forkexec/</link>
<description><![CDATA[ <p>With the typical fork+exec method of spawning an application, you are left in the dark about failures in the exec.  Once the fork occurs, the "main" process doesn't have any communication channel except waitpid, so it's hard to tell what happened.

With this function, a pipe is opened for the forked child to communicate errors.  If the exec succeeds, then the pipe is automatically closed, and the main process reports success.  Otherwise, the errno from exec is communicated through the pipe.</p> ]]></description>
<pubDate>Mon, 11 Dec 2006 17:55:15 GMT</pubDate>
<guid>http://snipplr.com/view/1790/safe-application-spawning-with-forkexec/</guid>
</item>
<item>
<title>(C++) C - create Process Daemon - whitetiger</title>
<link>http://snipplr.com/view/1629/c--create-process-daemon/</link>
<description><![CDATA[ <p></p> ]]></description>
<pubDate>Thu, 09 Nov 2006 23:55:41 GMT</pubDate>
<guid>http://snipplr.com/view/1629/c--create-process-daemon/</guid>
</item>
</channel>
</rss>