From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: Date: Wed, 21 Sep 2005 11:42:42 -0400 From: Russ Cox To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> Subject: Re: [9fans] thread confusion In-Reply-To: <200509211505.j8LF5FQ00275@zamenhof.cs.utwente.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <2e4165d0a4172357099de271ac66cd5e@lsub.org> <200509211505.j8LF5FQ00275@zamenhof.cs.utwente.nl> Topicbox-Message-UUID: 8e42e67e-ead0-11e9-9d60-3106f5b1d025 > My essential problem seems to be to 'shutdown' this pending library call = - > it will not time out by itself -- if indeed it does not react > to me closing the pipe, it will stay there forever. > But maybe I did something wrong there. You have to install a note handler, as Nemo said. But leave the proc alone and figure out the pipe close bug instead. The most likely problem is that you haven't actually closed the other side of the pipe completely. For example, maybe you have forked a child who inherited a copy of that fd, and that child is holding the pipe up. Programming with notes or signals is asking for trouble. Always. I'm sorry that threadint/threadkill are in the library. Russ