Re: FIFO blocking behaviour

[Edgar Fuß <ef%math.uni-bonn.de@localhost>]

> Are you sure you're not confusing this with the behaviour (which I *do*
> expect) of seeing the FIFO open block until a matching open is done?
Ah, sorry, that's probably it. So, is /that behaviour/ guaranteed?

Is it safe to have process A create the FIFO, pass the name to process B, 
open it for writing (write to it), and then "immediately" delete it?
Is it then guaranteed that process B will be able to open the FIFO (and, 
of course, read from it)?