zsh-users
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-users@sunsite.dk
Subject: Re: named pipes blocking zsh
Date: Wed, 01 Jun 2005 15:45:19 +0000	[thread overview]
Message-ID: <1050601154519.ZM11247@candle.brasslantern.com> (raw)
In-Reply-To: <d7kjph$ugg$1@sea.gmane.org>
In-Reply-To: <d7kjhd$ti9$1@sea.gmane.org>

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.


  parent reply	other threads:[~2005-06-01 15:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-01 14:18 Tim K. (Gmane)
2005-06-01 14:47 ` Bart Schaefer
2005-06-01 15:20   ` Tim K. (Gmane)
2005-06-01 15:36     ` Peter Stephenson
2005-06-01 15:45     ` Bart Schaefer [this message]
2005-06-01 15:24   ` Tim K. (Gmane)
2005-06-01 14:47 ` Peter Stephenson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1050601154519.ZM11247@candle.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-users@sunsite.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).