From: ts <decoux@...>
Date: 2003-12-13T22:41:09+09:00
Subject: Re: Bug with fifos in Linux?

>>>>> "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