From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10924 invoked by alias); 19 Jul 2013 21:36:30 -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: 31543 Received: (qmail 23258 invoked from network); 19 Jul 2013 21:36:15 -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=-2.6 required=5.0 tests=BAYES_00,HTML_MESSAGE, RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 Received-SPF: none (ns1.primenet.com.au: domain at brasslantern.com does not designate permitted sender hosts) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=wnIPoNNI2mDHPTifNVyraBt2DJowiYQdQNPQO+qj9Qc=; b=Jv8iSfbv6Iv28RIjkgKPBRixGWcwBq9PSlekhyrtzY/B9F+/DcyR6STMX+3/Ao5Akv z0yxfW16APBU8B7hmpa+qENTgjVAOQDa1hFX6RE2EmI6e48dm0BGri0jJo3W0yT84xGa 3iPQWi1/B0cDRrUb/TLBFelpVehsPoeTYV8yCm75dmUzniVZtRwX1+gqdU89UCh4dGpH V6cFWKtAuQalnu4vkGlEEvSax2CtifsHBQrHYIa9sAcbgHc+QZdBBAJhdxAF94WOAn0h 8r2J6IZFRmpyX+ZCtEPBqM6NL4tBVoD1ohHQyDkyMVmObF15UVTbKQmOhn43W6ZXsguF ITJA== MIME-Version: 1.0 X-Received: by 10.112.168.132 with SMTP id zw4mr8263075lbb.79.1374269767946; Fri, 19 Jul 2013 14:36:07 -0700 (PDT) In-Reply-To: <20130719200159.GA8712@chaz.gmail.com> References: <20130715133525.GA7694@chaz.gmail.com> <130715100624.ZM14123@torch.brasslantern.com> <20130716215540.22d88a27@pws-pc.ntlworld.com> <130717000027.ZM15643@torch.brasslantern.com> <20130717201733.2c0b029b@pws-pc.ntlworld.com> <20130718095741.3f54725f@pwslap01u.europe.root.pri> <20130718102227.527429bd@pwslap01u.europe.root.pri> <20130718123210.054f1ea1@pwslap01u.europe.root.pri> <20130719200159.GA8712@chaz.gmail.com> Date: Fri, 19 Jul 2013 14:36:07 -0700 Message-ID: Subject: Re: bug with eval, proc-subst and pipes From: Bart Schaefer To: Peter Stephenson , "zsh-workers@zsh.org" Content-Type: multipart/alternative; boundary=001a11c2349658256704e1e41d37 X-Gm-Message-State: ALoCoQmy2NBbNmdq6VF22PgFrH5AyBNdnfJDK3bP9gLaPyNMQSwvEQyb2iWZZLMwAHrMJGgcNdBM --001a11c2349658256704e1e41d37 Content-Type: text/plain; charset=ISO-8859-1 On Friday, July 19, 2013, Stephane Chazelas wrote: > 2013-07-18 12:32:10 +0100, Peter Stephenson: > [...] > > Apparently working (except for the fact it doesn't fix Stephane's > > original problem, don't know if we're any further forward with that). > > However, I'll wait in case Bart can see something I missed. For some reason I never received that message from Peter. Did it perhaps go privately to Stephen? ~$ eval 'ls -l <(echo 1) <(echo 2) <(echo 3) <(echo 4)' | cat > ls: cannot access /proc/self/fd/11: No such file or directory > ls: cannot access /proc/self/fd/13: No such file or directory > lr-x------ 1 chazelas chazelas 64 Jul 19 20:52 /proc/self/fd/10 -> > pipe:[509333] > lr-x------ 1 chazelas chazelas 64 Jul 19 20:52 /proc/self/fd/12 -> > pipe:[509335] Ok, this is kinda strange, because on my Ubuntu system there is no /proc/self/fd ... The "ls" shows /dev/fd files. Why would that be different? And it's further odd that some of the descriptors are closed but not all of them. > [In strace] > > See how fd 13 is closed in the process that execs ls and fd 11 > in its parent shortly before the fork. That's also odd. It would almost seem to imply that those descriptors got the close-on-exec flag set somehow. --001a11c2349658256704e1e41d37--