Re: libpthread fifo fdlock

2014-01-27 Thread Ted Unangst
On Mon, Jan 27, 2014 at 19:27, ido...@gmail.com wrote: > It was a peachy Sunday, Jan 26 2014, 22:05:25 when Marco Pfatschbacher > wrote: > >> On Sun, Jan 26, 2014 at 03:44:14PM -0500, ido...@gmail.com wrote: >> > Hi misc@, >> > From http://marc.info/?l=openbsd-cvs&m=133217901415880&w=2 >> > >> >

Re: libpthread fifo fdlock

2014-01-27 Thread idoadm
It was a peachy Sunday, Jan 26 2014, 22:05:25 when Marco Pfatschbacher wrote: > On Sun, Jan 26, 2014 at 03:44:14PM -0500, ido...@gmail.com wrote: > > Hi misc@, > > From http://marc.info/?l=openbsd-cvs&m=133217901415880&w=2 > > > > "The ``sleep until we have a writer'' behaviour of an open() on a

Re: libpthread fifo fdlock

2014-01-26 Thread Marco Pfatschbacher
On Sun, Jan 26, 2014 at 03:44:14PM -0500, ido...@gmail.com wrote: > Hi misc@, > From http://marc.info/?l=openbsd-cvs&m=133217901415880&w=2 > > "The ``sleep until we have a writer'' behaviour of an open() on a fifo > does so with the file descriptor table locked, so if we are waiting for > another

libpthread fifo fdlock

2014-01-26 Thread idoadm
Hi misc@, >From http://marc.info/?l=openbsd-cvs&m=133217901415880&w=2 "The ``sleep until we have a writer'' behaviour of an open() on a fifo does so with the file descriptor table locked, so if we are waiting for another thread to be our writer we will hang forever. Found this using zotero and fi