Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: PATCH: 3.0.6/3.1.6: Re: All sorts of file-descriptor strangeness
- X-seq: zsh-workers 8190
- From: Zefram <zefram@xxxxxxxx>
- To: schaefer@xxxxxxxxxxxxxxxxxxxxxxx (Bart Schaefer)
- 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)
- Cc: zefram@xxxxxxxx, zsh-workers@xxxxxxxxxxxxxx
- In-reply-to: <991010155440.ZM2271@xxxxxxxxxxxxxxxxxxxxxxx> from Bart Schaefer at "Oct 10, 1999 3:54:40 pm"
- Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm
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
Messages sorted by:
Reverse Date,
Date,
Thread,
Author