zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Peter Stephenson <p.stephenson@samsung.com>,
	"Zsh Hackers' List" <zsh-workers@zsh.org>
Subject: Re: <(...), >(...) and fds above 9
Date: Mon, 1 Jul 2019 13:06:36 -0700	[thread overview]
Message-ID: <CAH+w=7YBK+tN=gJ8oudt5jCD+aKwHBquXLLiNpnkksXK1hQJKA@mail.gmail.com> (raw)
In-Reply-To: <20190701200028.5ehhz6nsitc3bzfn@chaz.gmail.com>

On Mon, Jul 1, 2019 at 1:01 PM Stephane Chazelas
<stephane.chazelas@gmail.com> wrote:
>
> It looks like the key is *background* here, and it sounds like
> the reason is not so much about what the user expects but
> possibly some implementation limitation/consideration
>
> Is it documented anywhere that fds above 9 are closed for all
> commands started asynchronously?

This is a process security thing, to prevent rogue processes that
might be spawned from the shell having access to open files that they
shouldn't.

  reply	other threads:[~2019-07-01 20:07 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
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 [this message]
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='CAH+w=7YBK+tN=gJ8oudt5jCD+aKwHBquXLLiNpnkksXK1hQJKA@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --cc=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).