Re: leaks fd for internal functions but not external command

From	Sam Liddicott <sam@liddicott.com>
Newsgroups	gnu.bash.bug
Subject	Re: leaks fd for internal functions but not external command
Date	2019-07-23 16:15 +0100
Message-ID	<mailman.2078.1563894957.2688.bug-bash@gnu.org> (permalink)
References	<CAOj-5WDk=8kt=J8wO23giFVWRp5=_GbCNB2HQO87Upc4kkTg+g@mail.gmail.com> <5c34ecd5-c8b2-7000-46bc-1bbe3f71f163@case.edu> <CAOj-5WCFbUoU1x2aUvidT1opUbGeG2jFSaM__ch=SUAfzQbQ9w@mail.gmail.com> <78679ee9-fdaf-5180-d32f-81d92b936538@case.edu> <CAOj-5WBei5KMar7c967=jSwZRsW-Rz-0iL20TQMeuQoz61rfkw@mail.gmail.com>

Show all headers | View raw

On Tue, 23 Jul 2019 at 16:13, Chet Ramey <chet.ramey@case.edu> wrote:

> On 7/23/19 11:11 AM, Sam Liddicott wrote:
>
> > The report concerns the different behaviour with internal and external
> > operations.
>
> Right. The close-on-exec is deliberate. That's how it was intended.
>

Doesn't close-on-exec usually takes effect only on the process that does
the exec?
i.e. the fork that does the exec, not the parent process?

Sam

Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread

Thread

Re: leaks fd for internal functions but not external command Sam Liddicott <sam@liddicott.com> - 2019-07-23 16:15 +0100

csiph-web