From: Eric Will <rakaur@...>
Date: 2008-10-06T01:43:14+09:00
Subject: Re: stream closed (IOError)

On Sun, Oct 5, 2008 at 12:33 PM, Yukihiro Matsumoto <matz@ruby-lang.org> wrote:
> Since I still can not reproduce the problem, I can not say clearly, but:
>
> * timer callback may touch the socket right after it's closed.
> * you've mixed fork and threads, which may not work properly.
> * you don't need timeout.rb.  try attached simpler version.

Thanks. I should have thought of that to begin with. :)

It doesn't have to do with fork. In all my tests I run it with
--nofork (which skips forking). The only thing using threads was
timer.rb.

Googling found me some Japanese posts, but that didn't help. The rest
seemed to be fixed by checking socket#closed? first.

Thanks so much.

>
>                                                        matz.
>

-- Eric Will