title: O_RDWR on named pipes with poll()
body: <p>I have gone through a variaty of different linux named pipe client/server implementations but most of them use the blocking defaults on reads/writes.</p>
  
  <p>As I am already using poll() to check other flags I though it would be a good idea to check for incoming FIFO data via poll() as well...</p>
  
  <p>After all the research I think that opening the pipe in O_RDWR mode is the only way to prevent an indefinitely number of EOF events on a pipe when no writer has opened it.</p>
  
  <p>This way both ends of the pipe are closed and other clients can open the writable end as well. To respond back I would use separate pipes...</p>
  
  <p>My problem is that although I have found some examples that use the O_RDWR flag the open() manpages describe this flag as being unefined when assigned to a FIFO. (<a href="http://linux.die.net/man/3/open">http://linux.die.net/man/3/open</a>) </p>
  
  <p>But how would you use poll() on a pipe without O_RDWR? Do you think "O_RDWR" is a legitimate way to open pipes???</p>