From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-31674-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 26075 invoked by alias); 27 Aug 2013 12:12:14 -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: 31674
Received: (qmail 16397 invoked from network); 27 Aug 2013 12:12:08 -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: cbfec7f4-b7f0a6d000007b1b-49-521c9538e5f8
Date: Tue, 27 Aug 2013 13:01:59 +0100
From: Peter Stephenson <p.stephenson@samsung.com>
To: zsh-workers@zsh.org
Subject: Re: zpty non-functional?
Message-id: <20130827130159.4dcd7ef7@pwslap01u.europe.root.pri>
In-reply-to: <130826175421.ZM16713@torch.brasslantern.com>
References: <20130824124422.GA14766@mugenguild.com>
 <130824131041.ZM15573@torch.brasslantern.com>
 <20130824224839.5830e7fd@pws-pc.ntlworld.com>
 <130824170157.ZM15713@torch.brasslantern.com>
 <20130825195946.2f9799c6@pws-pc.ntlworld.com>
 <130825150104.ZM15563@torch.brasslantern.com>
 <20130826203305.013d0ca2@pws-pc.ntlworld.com>
 <130826175421.ZM16713@torch.brasslantern.com>
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=US-ASCII
Content-transfer-encoding: 7bit
X-Brightmail-Tracker:
 H4sIAAAAAAAAA+NgFupjluLIzCtJLcpLzFFi42I5/e/4ZV2LqTJBBuf/61ocbH7I5MDoserg
	B6YAxigum5TUnMyy1CJ9uwSujP/r1zMVrGet+Df1GXsD4ySWLkZODgkBE4nFiy+xQ9hiEhfu
	rWfrYuTiEBJYyihxeds5FghnOZPEqznrmEGqWARUJTq+rGMEsdkEDCWmbpoNZosIiEucXXse
	bKqwgKLE68Y7rCA2r4C9xM8zi8E2cApYSWz8/p4ZYmgzs8TzttdgDfwC+hJX/35igjjDXmLm
	lTOMEM2CEj8m3wOrYRbQkti8rYkVwpaX2LzmLfMERoFZSMpmISmbhaRsASPzKkbR1NLkguKk
	9FxDveLE3OLSvHS95PzcTYyQMPyyg3HxMatDjAIcjEo8vA9apIOEWBPLiitzDzFKcDArifBO
	bZYJEuJNSaysSi3Kjy8qzUktPsTIxMEp1cCoIMkmNUNpS7nD3LuKLlufhPeyCAj7LUjunJcw
	37pnNnuiVSzDXbGWt3Uz/4T+PXFgZfGrS9/yliht2vJm0cK75v5uygXWyUv2xE0V19x2eTH/
	r1krds574ffbe/rpnQemKK/JusplvFObsySy1ilt/Y75SuWXGnRFI162cbWvv1/pcFP8npKD
	EktxRqKhFnNRcSIAuO4yAyECAAA=

On Mon, 26 Aug 2013 17:54:21 -0700
Bart Schaefer <schaefer@brasslantern.com> wrote:
> On Aug 26,  8:33pm, Peter Stephenson wrote:
> }
> } Here's a synch, as well as a test that was showing up the problem
> 
> It just occurred to me that if the syncch [why two c?] trick solves
> the race, then it's probably not even necessary to write a byte on
> the pipe -- just close it in the child, and the parent will get EOF.

syncch is "sync ch[ar]".

All I've added is the read and write --- the pipe was there anyway as
the key part of the master/slave interface.  So this is about as minimal
as we get, up to tests and loops I may have added that we don't really
need.

pws