After way too much time, I figured it out, after a quote from [this
post](http://fixunix.com/questions/379652-sending-eof-named-pipe.html)
jumped out at me:
> See the "I/O on Pipes and FIFOs" section of pipe(7) ("man 7 pipe")
>
> "If all file descriptors referring to the write end of a pipe have
>
Anybody else see this issue?
On Thu, Feb 10, 2011 at 10:37 AM, Yang Zhang wrote:
> On Thu, Feb 10, 2011 at 12:28 AM, Jean-Michel Pichavant
> wrote:
>> Yang Zhang wrote:
>>>
>>> On Wed, Feb 9, 2011 at 11:01 AM, MRAB wrote:
>>>
On 09/02/2011 01:59, Yang Zhang wrote:
>
> I r
On Thu, Feb 10, 2011 at 12:28 AM, Jean-Michel Pichavant
wrote:
> Yang Zhang wrote:
>>
>> On Wed, Feb 9, 2011 at 11:01 AM, MRAB wrote:
>>
>>>
>>> On 09/02/2011 01:59, Yang Zhang wrote:
>>>
I reduced a problem I was seeing in my application down into the
following test case. In this
Yang Zhang wrote:
On Wed, Feb 9, 2011 at 11:01 AM, MRAB wrote:
On 09/02/2011 01:59, Yang Zhang wrote:
I reduced a problem I was seeing in my application down into the
following test case. In this code, a parent process concurrently
spawns 2 (you can spawn more) subprocesses that read a
On Wed, Feb 9, 2011 at 11:01 AM, MRAB wrote:
> On 09/02/2011 01:59, Yang Zhang wrote:
>>
>> I reduced a problem I was seeing in my application down into the
>> following test case. In this code, a parent process concurrently
>> spawns 2 (you can spawn more) subprocesses that read a big message
>>
On 09/02/2011 01:59, Yang Zhang wrote:
I reduced a problem I was seeing in my application down into the
following test case. In this code, a parent process concurrently
spawns 2 (you can spawn more) subprocesses that read a big message
from the parent over stdin, sleep for 5 seconds, and write so
I reduced a problem I was seeing in my application down into the
following test case. In this code, a parent process concurrently
spawns 2 (you can spawn more) subprocesses that read a big message
from the parent over stdin, sleep for 5 seconds, and write something
back. However, there's unexpected
