From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4547 invoked by alias); 29 Sep 2014 14:13:44 -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: 19185 Received: (qmail 13835 invoked from network); 29 Sep 2014 14:13:42 -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 X-AuditID: cbfec7f5-b7f776d000003e54-89-542966b8a92e Date: Mon, 29 Sep 2014 15:03:35 +0100 From: Peter Stephenson To: zsh-users@zsh.org Subject: Re: File descriptor leakage? Message-id: <20140929150335.472ec4b8@pwslap01u.europe.root.pri> In-reply-to: <20140929135851.GA12969@lilyforest> References: <20140929035338.GA29747@lilyforest> <140928230710.ZM5202@torch.brasslantern.com> <20140929115901.255bacb9@pwslap01u.europe.root.pri> <20140929135851.GA12969@lilyforest> 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+NgFuplluLIzCtJLcpLzFFi42I5/e/4Fd0daZohBlPPiljsOLmS0YHRY9XB D0wBjFFcNimpOZllqUX6dglcGb/b5rMW7GeuaNtzl7GB8TlTFyMnh4SAicSBjh+MELaYxIV7 69lAbCGBpYwSax4adjFygdhMEj/aHjGDJFgEVCX+rTsE1swmYCgxddNssGYRAVGJ5Ss2s4PY wkA1Wy+2gA3iFbCXuP3uDlgvp4CBxJpzt9gghu5ilHj3/zhYM7+AvsTVv5+gLrKXmHnlDCNE s6DEj8n3WEBsZgEtic3bmlghbHmJzWveMk9gFJiFpGwWkrJZSMoWMDKvYhRNLU0uKE5KzzXS K07MLS7NS9dLzs/dxAgJwq87GJceszrEKMDBqMTDy7FCI0SINbGsuDL3EKMEB7OSCK9dimaI EG9KYmVValF+fFFpTmrxIUYmDk6pBsa6I8VbjY4v/BOyQD56/Yfll7ouPL65VnHP1dYKa76f 7lmLE9nTrHLfX2jUMNdiL49g2z/nuVeM1sKbk3+u3Rap9Hzhyca1S5OevbCJsIlsKL30ZsaW h8Yn+z7fWrtVw+zh/qnBv/S1X/Xyd3omu1bZcivsPGNu5VewQODcvb/3tXzjMztbTeyVWIoz Eg21mIuKEwHElK7DIAIAAA== On Mon, 29 Sep 2014 21:58:51 +0800 lilydjwg wrote: > Hi, I'm sorry I didn't test master. It turns out that this has already > been fix at commit 4414e54ea7ffe50acca851c11c2ef49dc867c55d Great. > And the patch above doesn't fix it for me (patched against that bad commit). I wouldn't expect it to, since there's no sign anything was actually failing apart from the leak; it's just tidying up another hole. pws