<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Named pipes</title>
	<atom:link href="http://maas-frensch.com/peter/2006/07/23/named-pipes/feed/" rel="self" type="application/rss+xml" />
	<link>http://maas-frensch.com/peter/2006/07/23/named-pipes/</link>
	<description>Peter Maas's Weblog</description>
	<pubDate>Thu, 16 Oct 2008 02:01:31 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Named pipes in OSX? at log4p</title>
		<link>http://maas-frensch.com/peter/2006/07/23/named-pipes/#comment-3872</link>
		<dc:creator>Named pipes in OSX? at log4p</dc:creator>
		<pubDate>Tue, 29 May 2007 08:46:23 +0000</pubDate>
		<guid isPermaLink="false">http://maas-frensch.com/peter/2006/07/23/named-pipes/#comment-3872</guid>
		<description>[...] previously I wrote about using named pipes to avoid temporary files when working from the CLI. The odd thing is that the following command seems to work on bash/linux but responds with an error message (curl: (23) Failed writing body) on bash/OSX diff [...]</description>
		<content:encoded><![CDATA[<p>[...] previously I wrote about using named pipes to avoid temporary files when working from the CLI. The odd thing is that the following command seems to work on bash/linux but responds with an error message (curl: (23) Failed writing body) on bash/OSX diff [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
