From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20470 invoked from network); 1 Jun 2005 15:49:46 -0000 Received: from news.dotsrc.org (HELO a.mx.sunsite.dk) (130.225.247.88) by ns1.primenet.com.au with SMTP; 1 Jun 2005 15:49:46 -0000 Received: (qmail 87476 invoked from network); 1 Jun 2005 15:49:39 -0000 Received: from sunsite.dk (130.225.247.90) by a.mx.sunsite.dk with SMTP; 1 Jun 2005 15:49:39 -0000 Received: (qmail 8128 invoked by alias); 1 Jun 2005 15:49:33 -0000 Mailing-List: contact zsh-users-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 8934 Received: (qmail 8119 invoked from network); 1 Jun 2005 15:49:32 -0000 Received: from news.dotsrc.org (HELO a.mx.sunsite.dk) (130.225.247.88) by sunsite.dk with SMTP; 1 Jun 2005 15:49:32 -0000 Received: (qmail 86389 invoked from network); 1 Jun 2005 15:49:32 -0000 Received: from vms048pub.verizon.net (206.46.252.48) by a.mx.sunsite.dk with SMTP; 1 Jun 2005 15:49:26 -0000 Received: from candle.brasslantern.com ([4.11.1.68]) by vms048.mailsrvcs.net (Sun Java System Messaging Server 6.2 HotFix 0.04 (built Dec 24 2004)) with ESMTPA id <0IHE00LBCX3KAR60@vms048.mailsrvcs.net> for zsh-users@sunsite.dk; Wed, 01 Jun 2005 10:45:21 -0500 (CDT) Received: from candle.brasslantern.com (IDENT:schaefer@localhost [127.0.0.1]) by candle.brasslantern.com (8.12.11/8.12.11) with ESMTP id j51FjKda011249 for ; Wed, 01 Jun 2005 08:45:20 -0700 Received: (from schaefer@localhost) by candle.brasslantern.com (8.12.11/8.12.11/Submit) id j51FjJAr011248 for zsh-users@sunsite.dk; Wed, 01 Jun 2005 08:45:19 -0700 Date: Wed, 01 Jun 2005 15:45:19 +0000 From: Bart Schaefer Subject: Re: named pipes blocking zsh In-reply-to: In-reply-to: To: zsh-users@sunsite.dk Message-id: <1050601154519.ZM11247@candle.brasslantern.com> MIME-version: 1.0 X-Mailer: Z-Mail (5.0.0 30July97) Content-type: text/plain; charset=us-ascii References: <1050601144728.ZM11059@candle.brasslantern.com> Comments: In reply to "Tim K. (Gmane)" "Re: named pipes blocking zsh" (Jun 1, 8:24am) Comments: In reply to "Tim K. (Gmane)" "Re: named pipes blocking zsh" (Jun 1, 8:20am) X-Spam-Checker-Version: SpamAssassin 3.0.2 on a.mx.sunsite.dk X-Spam-Level: X-Spam-Status: No, score=-2.6 required=6.0 tests=AWL,BAYES_00 autolearn=ham version=3.0.2 X-Spam-Hits: -2.6 On Jun 1, 8:24am, Tim K. (Gmane) wrote: } } Now that I think about it, what if the pine process crashed and } didn't have a chance to send an EOF or remove the pipe (assuming pine } implemented the EOF)? A crash that severe is by definition an unrecoverable error; it's not possible to write code to handle it, and it's certainly not zsh's job to attempt to handle unrecoverable errors in other arbitrary programs. On Jun 1, 8:20am, Tim K. (Gmane) wrote: } Subject: Re: named pipes blocking zsh } } What's interesting is that if I 'strace' the zsh process while it's } stuck (after the pipe was deleted), it will terminate. That's almost certainly because strace sends a SIGPROF to zsh, which interrupts whatever system call was blocking on the fifo. I suspect that if you attempted something other than "kill -9" (such as, say, "kill -1") you'd find that it *is* possible to politely interrupt zsh when it's waiting on the fifo.