From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26370 invoked by alias); 29 Feb 2016 09:50:01 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 38045 Received: (qmail 5543 invoked from network); 29 Feb 2016 09:49:59 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) 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.1 X-AuditID: cbfec7f5-f79b16d000005389-f0-56d411e95188 Date: Mon, 29 Feb 2016 09:39:50 +0000 From: Peter Stephenson To: Zsh hackers list Subject: Re: [bug?] Invalid file descriptor ignored Message-id: <20160229093950.30f4c0d4@pwslap01u.europe.root.pri> In-reply-to: <56D3E8E4.6090007@inlv.org> References: <56D3E8E4.6090007@inlv.org> 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+NgFjrHLMWRmVeSWpSXmKPExsVy+t/xK7ovBa+EGVzrZbI42PyQyYHRY9XB D0wBjFFcNimpOZllqUX6dglcGf8eRhe0sFRM/HWSsYFxPnMXIyeHhICJxIW+O0wQtpjEhXvr 2boYuTiEBJYySsx99BHKmcEkMeXyWbAOIYFzjBIXDwlC2GcZJS51lYHYLAKqEr8vrAGrYRMw lJi6aTYjiC0ioCWx4+RJsA3CAsYSy/7sArN5BewlJix/BFbPKaAhcbL1GivETHWJjtPbwGx+ AX2Jq38/QV1nLzHzyhlGiF5BiR+T77GA2MxA8zdva2KFsOUlNq95ywwz58bd3ewTGIVnIWmZ haRlFpKWBYzMqxhFU0uTC4qT0nON9IoTc4tL89L1kvNzNzFCQvnrDsalx6wOMQpwMCrx8L7Q vBwmxJpYVlyZe4hRgoNZSYT3+R+gEG9KYmVValF+fFFpTmrxIUZpDhYlcd6Zu96HCAmkJ5ak ZqemFqQWwWSZODilGhglvurrRz8rWpl5tdBd/uH52zM+bLSY1ll2Pfq20pR9znefHLvCl9A9 e17KwubqiRlyoTb54mtd0yXLd12T+yWTJRTIF79TeOmJxHuskxwulQc9FUgvqnEtuHxM78ex iF/VPBeMXk3WUZq59tuFkkhm+xMWwcIGnUr20z3qVR2mPl0fNVV35jYlluKMREMt5qLiRADU 7I1xYQIAAA== On Mon, 29 Feb 2016 07:44:52 +0100 Martijn Dekker wrote: > There is some strange and inconsistent behaviour when trying to write to > a non-open file descriptor. Yes, I noticed not so long ago that some cases got changed so any error was deliberately ignored. Bart pointed out an ancient message on the mailing list about this. I can't remember what that discussion was about now, though... it doesn't appear to be the discussion about management of fdtable from mid October. pws