From: "Tim K. (Gmane)" <tk-gmane+at@idpax.com>
To: zsh-users@sunsite.dk
Subject: named pipes blocking zsh
Date: Wed, 01 Jun 2005 07:18:38 -0700 [thread overview]
Message-ID: <d7kfuc$gem$1@sea.gmane.org> (raw)
Hello,
I have a situtation with zsh: I use pine as my mail reader and it has a
feature where it can create a named pipe (FIFO) and write to it when new
mail arrives. Naturally, I thought of writing a script at the other end
of the pipe that reads the messages and sends me notifications in some
other way.
The way I have it set up is to have a zsh script that starts another
"notify" child zsh script that reads from the pipe and does its
notification thing and then the main script calls pine.
This all seems to work, except when I quit pine, hence terminating the
main "parent" script, the child "notify" script does not exit, it's
stuck reading from the pipe (even though the pipe is deleted). The child
script becomes owned by PPID 1 and the only way to kill it is kill -9 ...
I'm reading with the built in "read var < pine_pipe" which blocks until
the first line of data is written to the pipe by pine. I also tried
"read -t" but it doesn't react to the timeout. Also tried the zselect
module, with and without timeouts, nothing works. If there's nothing in
the pipe, the zsh process just hangs until there is data.
My current workaround is to trap the exits from the main script and kill
-9 the child script. This works fine almost all the time except when the
main script itself is killed and it doesn't have a chance to kill it's
child. For this I made the notify script clean up any running instances
of itself when it comes up (but there's still that window of time where
there's a zsh process around that refuses to die).
Is there anything in particular I should be aware of with these named
pipes? I'm using zsh 4.2.1 if it makes a difference ...
Thanks for your help.
--
Tim
next reply other threads:[~2005-06-01 14:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-01 14:18 Tim K. (Gmane) [this message]
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
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='d7kfuc$gem$1@sea.gmane.org' \
--to=tk-gmane+at@idpax.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).