From: Derek Lewis <lewisd@...00f.net>
Date: 2003-12-14T03:12:31+09:00
Subject: Re: Bug with fifos in Linux?


Oh, well I guess that settles it. :)  Thanks.  I should be able to come up
with something workable, now that I know what's going on.

On Sat, 13 Dec 2003, ts wrote:

> >>>>> "D" == Derek Lewis <lewisd@f00f.net> writes:
>
> D> Is there a reason ruby behaves like this, rather than having the open
> D> calls succeede without blocking (provided the file exists), and having the
> D> blocking happen on the read/write calls?  My only past experience with
> D> reading/writing fifos was in Java, and that was how it behaved, if memory
> D> serves me correctly.
>
>  Well the best question is : Is there a reason linux behave like this
>  ... :-)
>
>
> svg% man fifo
> FIFO(4)                    Linux Programmer's Manual                   FIFO(4)
>
> NAME
>        fifo - first-in first-out special file, named pipe
> [...]
>        A  process  can open a FIFO in non-blocking mode. In this case, opening
>        for read only will succeed even if noone has opened on the  write  side
>        yet;  opening  for  write  only will fail with ENXIO (no such device or
>        address) unless the other end has already been opened.
> [...]
> svg%
>
>
> Guy Decoux
>

Derek Lewis

===================================================================
      Java Web-Application Developer

      Email    : email@lewisd.com
      Cellular : 604.312.2846
      Website  : http://www.lewisd.com

 "If you've got a 5000-line JSP page that has "all in one" support
 for three input forms and four follow-up screens, all controlled
 by "if" statements in scriptlets, well ... please don't show it
 to me :-).  Its almost dinner time, and I don't want to lose my
 appetite :-)."
      - Craig R. McClanahan