From: Jamie Herre <jlst@...>
Date: 2004-05-07T03:32:20+09:00
Subject: Re: ruby_connect's error handling


On May 5, 2004, at 7:01 PM, Martin Dorey wrote:

> I can add to that from my experience today - when my linux box returned
> EPIPE in this situation.  Here's hopefully all of the relevant parts 
> of an
> strace of a ruby program running on:
>

I can't address your discussion of multiple connect()'s in the presence 
of signals but I can say that the 'some platforms' referred to in the 
socket.c code was meant for Darwin.  Linux has not been a problem in 
this regard before.

EPIPE seems strange.  It's not listed as a possible return code on 
Linux's connect(2) man page.  Is your ruby using '--enable-pthread'?  
Does your script have any open pipes?