From: Peter Stephenson <p.stephenson@samsung.com>
To: <zsh-workers@zsh.org>
Subject: Re: <(...), >(...) and fds above 9
Date: Mon, 1 Jul 2019 16:28:28 +0100 [thread overview]
Message-ID: <1561994908.6006.19.camel@samsung.com> (raw)
In-Reply-To: <CAH+w=7Z+UBP-0ZvHbNzfz13a7e4AFGpQyuntEaKNENeLRDdmVQ@mail.gmail.com>
On Mon, 2019-07-01 at 07:39 -0700, Bart Schaefer wrote:
> On Mon, Jul 1, 2019 at 3:09 AM Peter Stephenson
> <p.stephenson@samsung.com> wrote:
> >
> >
> > On Mon, 2019-07-01 at 11:00 +0100, Stephane Chazelas wrote:
> > >
> > >
> > > It seems fds above 9 are closed in those forms of process substitutions.
> > >
> > > It doesn't happen for the =(...) form of process substitution.
> > >
> > > Is that intentional?
> > I'd be surprised if there was any deliberate intention to make these different,
> > but there may be some detail I can't think of.
> <(...) does
> entersubsh(ESUB_ASYNC|ESUB_PGRP, NULL);
>
> whereas =(...) does
> entersubsh(ESUB_PGRP|ESUB_NOMONITOR, NULL);
>
> The fds above 9 are only closed for ASYNC, I think.
I don't think entersubsh() calls closem() --- it's
usually done at other points, either in execute()
or a special execution function in the case of the
various process-style substitutions.
Looks like =(...) doesn't call closem() at all when
forking, hence the difference in behaviour. So
=(...) is the odd one out.
pws
next prev parent reply other threads:[~2019-07-01 15:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20190701100058epcas2p25e5f8dbd14d048fe2be1d831f3cf60ab@epcas2p2.samsung.com>
2019-07-01 10:00 ` Stephane Chazelas
2019-07-01 10:08 ` Peter Stephenson
2019-07-01 14:39 ` Bart Schaefer
2019-07-01 15:28 ` Peter Stephenson [this message]
2019-07-01 16:22 ` Stephane Chazelas
2019-07-01 16:52 ` Peter Stephenson
2019-07-01 17:00 ` Peter Stephenson
2019-07-01 20:00 ` Stephane Chazelas
2019-07-01 20:06 ` Bart Schaefer
2019-07-02 8:59 ` Peter Stephenson
2019-07-02 12:20 ` Stephane Chazelas
2019-07-02 13:12 ` Peter Stephenson
2019-07-02 15:19 ` Stephane Chazelas
2019-07-02 15:21 ` Peter Stephenson
2019-07-02 16:43 ` Sebastian Gniazdowski
2019-07-02 18:08 ` Stephane Chazelas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1561994908.6006.19.camel@samsung.com \
--to=p.stephenson@samsung.com \
--cc=zsh-workers@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).