zsh-workers
 help / color / mirror / code / Atom feed
From: Zefram <zefram@fysh.org>
To: schaefer@candle.brasslantern.com (Bart Schaefer)
Cc: zefram@fysh.org, zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: 3.0.6/3.1.6: Re: All sorts of file-descriptor strangeness
Date: Sun, 10 Oct 1999 18:41:46 +0100 (BST)	[thread overview]
Message-ID: <E11aMyg-0008VI-00@crucigera.fysh.org> (raw)
In-Reply-To: <991010155440.ZM2271@candle.brasslantern.com> from Bart Schaefer at "Oct 10, 1999  3:54:40 pm"

Bart Schaefer wrote:
>If we continue to limit the FDs on the LHS to 0-9, then we can simply
>report EBADF whenever one of the "private" FDs appears on the RHS.

Ah yes, a neat solution.  This is definitely an improvement over my patch,
and doesn't require use to actually shuffle private fds around at all.

>I'd further point out that with the /proc/*/fd filesystem available, the
>shell would have to go to nearly impossible lengths to prevent its private
>FDs from becoming visible;

That's a slightly different matter.  The shell provides a view of a set
of fds which gets passed on to programs run from the shell; this is what
the redirections manipulate.  Conceptually it has no inherent connection
with the actual OS-level fd table of the shell process.  Anyone that
fiddles with /proc/*/fd for a process that they don't actually control
at the fd level is just asking for trouble.

-zefram


  parent reply	other threads:[~1999-10-10 17:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-05  9:45 Bart Schaefer
1999-10-10  8:27 ` PATCH: 3.0.6/3.1.6: " Bart Schaefer
1999-10-10 13:35   ` Zefram
1999-10-10 15:54     ` Bart Schaefer
1999-10-10 16:39       ` PATCH: Re: PATCH: no more fd mixups Bart Schaefer
1999-10-10 17:53         ` Zefram
1999-10-10 21:11           ` PATCH: 3.0.6/3.1.6: Re: All sorts of file-descriptor strangeness Bart Schaefer
1999-10-11  8:12             ` Zefram
1999-10-10 17:41       ` Zefram [this message]
1999-10-10 14:35 PATCH: no more fd mixups Zefram

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=E11aMyg-0008VI-00@crucigera.fysh.org \
    --to=zefram@fysh.org \
    --cc=schaefer@candle.brasslantern.com \
    --cc=zsh-workers@sunsite.auc.dk \
    /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).