From: Peter Stephenson <p.stephenson@samsung.com>
To: zsh-users@zsh.org
Subject: Re: Implicit killing of subprocesses
Date: Wed, 28 Aug 2013 14:26:51 +0100 [thread overview]
Message-ID: <20130828142651.4c930ba4@pwslap01u.europe.root.pri> (raw)
In-Reply-To: <521DF308.4040106@necoro.eu>
On Wed, 28 Aug 2013 14:54:32 +0200
René Neumann <lists@necoro.eu> wrote:
> When I use
>
> coproc dbus-monitor
> while read -p line; do ... done
>
> the dbus-monitor process lurks around after the script finishes
> (breaking or returning from the loop).
Hmm... assuming this is interactive, you should see enough job control
messages to alert you to what's going on. With no options set, it would
be something like:
% coproc cat
[1] 4757
% exit
zsh: you have running jobs.
% exit
zsh: warning: 1 jobs SIGHUPe
indicating the coprocess has been sent SIGHUP. If you had the NOHUP
option set, it would still warn you but it wouldn't send SIGHUP.
Not sure what happens non-interactively, coproc is really there for use
with job control.
pws
next prev parent reply other threads:[~2013-08-28 13:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-28 12:54 René Neumann
2013-08-28 13:02 ` René Neumann
2013-08-28 13:26 ` Peter Stephenson [this message]
2013-08-28 13:38 ` René Neumann
2013-08-28 13:47 ` Peter Stephenson
2013-08-28 15:59 ` Bart Schaefer
2013-08-28 16:11 ` Peter Stephenson
2013-08-28 16:27 ` René Neumann
2013-08-29 0:20 ` Bart Schaefer
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=20130828142651.4c930ba4@pwslap01u.europe.root.pri \
--to=p.stephenson@samsung.com \
--cc=zsh-users@zsh.org \
/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).