Version française
Home     About     Download     Resources     Contact us    

This site is updated infrequently. For up-to-date information, please visit the new OCaml website at

Browse thread
Named pipe problem: is this a bug?
[ Home ] [ Index: by date | by threads ]
[ Search: ]

[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: -- (:)
From: Richard Jones <rich@a...>
Subject: Re: [Caml-list] Named pipe problem: is this a bug?
This is documented behaviour.  You can't open a FIFO in read mode
until a writer has opened the FIFO - instead the open(2) syscall will
block.  You can pass the O_NONBLOCK flag to open, in which case the
open call will not block.  Or you can open for read and write (because
you yourself are then supplying a writer).

Some more details here:


Richard Jones, CTO Merjis Ltd.
Merjis - web marketing and technology -
Team Notepad - intranets and extranets for business -