Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #15216
| From | Greg Wooledge <wooledg@eeg.ccf.org> |
|---|---|
| Newsgroups | gnu.bash.bug |
| Subject | Re: leaks fd for internal functions but not external command |
| Date | 2019-07-23 11:52 -0400 |
| Message-ID | <mailman.2086.1563897210.2688.bug-bash@gnu.org> (permalink) |
| References | (4 earlier) <CAOj-5WBei5KMar7c967=jSwZRsW-Rz-0iL20TQMeuQoz61rfkw@mail.gmail.com> <CAOj-5WA_URW5b7a2EU+rR=T_wbTDEpOM_PSo9yNyU-Dqj+cWaA@mail.gmail.com> <f6acdcca-4c7c-b05c-004d-9b8ceab1e169@case.edu> <CAOj-5WA0b5Lv9GhXkK6gwoS1uVd2B1a0048tZ6sUNnhVHS+ixg@mail.gmail.com> <20190723155218.GG1218@eeg.ccf.org> |
On Tue, Jul 23, 2019 at 04:40:03PM +0100, Sam Liddicott wrote:
> Is using {xxx}>... suppose to give me a file handle I can use as I wish (as
> you say), or not?
>
> Using explicit descriptors e.g. 10>... behaves consistently whether the the
> command is internal or external.
>
> Having bash allocate the descriptor is not consistent.
>
> Sam
I'm getting major deja vu here.
https://lists.gnu.org/archive/html/bug-bash/2012-11/msg00082.html
Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread
Re: leaks fd for internal functions but not external command Greg Wooledge <wooledg@eeg.ccf.org> - 2019-07-23 11:52 -0400
csiph-web