From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-36189-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 17052 invoked by alias); 16 Aug 2015 17:37:24 -0000
Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
X-Seq: 36189
Received: (qmail 23690 invoked from network); 16 Aug 2015 17:37:22 -0000
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on f.primenet.com.au
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.0
X-Originating-IP: [80.3.228.158]
X-Spam: 0
X-Authority: v=2.1 cv=dtgmcAU4 c=1 sm=1 tr=0 a=P+FLVI8RzFchTbbqTxIDRw==:117
 a=P+FLVI8RzFchTbbqTxIDRw==:17 a=NLZqzBF-AAAA:8 a=kj9zAlcOel0A:10
 a=q2GGsy2AAAAA:8 a=K21ms-xJE-FnYESbttwA:9 a=CjuIK1q_8ugA:10
Date: Sun, 16 Aug 2015 18:37:15 +0100
From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh-workers@zsh.org
Subject: Re: 5.0.8 regression when waiting for suspended jobs
Message-ID: <20150816183715.034adb8b@ntlworld.com>
In-Reply-To: <150814185632.ZM16733@torch.brasslantern.com>
References: <87wpxhk970.fsf@gmail.com>
	<150730123904.ZM11774@torch.brasslantern.com>
	<87si84k9uf.fsf@gmail.com>
	<150731085638.ZM15733@torch.brasslantern.com>
	<150811165655.ZM31504@torch.brasslantern.com>
	<20150812104351.65a4cbea@pwslap01u.europe.root.pri>
	<150812075858.ZM32741@torch.brasslantern.com>
	<20150812170904.2c0e78de@pwslap01u.europe.root.pri>
	<150812103100.ZM13899@torch.brasslantern.com>
	<150814185632.ZM16733@torch.brasslantern.com>
X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.28; x86_64-redhat-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Fri, 14 Aug 2015 18:56:31 -0700
Bart Schaefer <schaefer@brasslantern.com> wrote:
> (1) Go for a minimal change of sending the SIGCONT only when !wait_cmd,
> which ends up with us blocking forever as with 5.0.7 and before (but
> blocked on signal_suspend() rather than busy-waiting, which is good).

I think I could live with this.

It's getting to the point where it doesn't look all that helpful to
agonise much further unless users have postgraduate degrees in job
control software.

pws