From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6059 invoked by alias); 28 Aug 2013 13:27:23 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: X-Seq: 17947 Received: (qmail 7707 invoked from network); 28 Aug 2013 13:27:17 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-6.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_HI, SPF_HELO_PASS autolearn=ham version=3.3.2 Received-SPF: none (ns1.primenet.com.au: domain at samsung.com does not designate permitted sender hosts) X-AuditID: cbfec7f5-b7ef66d00000795a-25-521dfa9dfa35 Date: Wed, 28 Aug 2013 14:26:51 +0100 From: Peter Stephenson To: zsh-users@zsh.org Subject: Re: Implicit killing of subprocesses Message-id: <20130828142651.4c930ba4@pwslap01u.europe.root.pri> In-reply-to: <521DF308.4040106@necoro.eu> References: <521DF308.4040106@necoro.eu> Organization: Samsung Cambridge Solution Centre X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.0; i386-redhat-linux-gnu) MIME-version: 1.0 Content-type: text/plain; charset=UTF-8 Content-transfer-encoding: quoted-printable X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFuplluLIzCtJLcpLzFFi42I5/e/4Fd25v2SDDE4eZLTYcXIlowOjx6qD H5gCGKO4bFJSczLLUov07RK4Mm7dnc5S0MtW0ff8DXMD43OWLkZODgkBE4nPDfeYIWwxiQv3 1rN1MXJxCAksZZSYev43E5TDJLG+7xEjSBWLgKrE6Ys32UFsNgFDiambZoPFRQREJZav2AwW FxbQlbh8vokNxOYVsJe4creJFcTmFNCUuHrkApgtJKAh8enoa7AafgF9iat/PzFBXGEvMfPK GUaIXkGJH5PvgV3KLKAuMWneImYIW1viybsLrBMYBWYhKZuFpGwWkrIFjMyrGEVTS5MLipPS c430ihNzi0vz0vWS83M3MUKC8OsOxqXHrA4xCnAwKvHwMvyUDRJiTSwrrsw9xCjBwawkwsu/ HSjEm5JYWZValB9fVJqTWnyIkYmDU6qBkf1kPadSqZhDZm5c/JtlZa0XmoKMP9TOfF4ld0Bg 5iYuq1sn1AqVZ55Oe+fGt+yJZL5R10f/0mQLvhXPryzjcejQ+suV7NepfMHqh2h37ul/uT94 vu4J7Jok4teaeszylhrLp7kz03zfND/5pOOsrRB9/FfS/Nx5PnylM63XXO5czRt7b6e4Ektx RqKhFnNRcSIAedg8ACACAAA= On Wed, 28 Aug 2013 14:54:32 +0200 Ren=C3=A9 Neumann wrote: > When I use >=20 > coproc dbus-monitor > while read -p line; do ... done >=20 > 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