Re: leaks fd for internal functions but not external command

From	Chet Ramey <chet.ramey@case.edu>
Newsgroups	gnu.bash.bug
Subject	Re: leaks fd for internal functions but not external command
Date	2019-07-23 11:18 -0400
Message-ID	<mailman.2079.1563895112.2688.bug-bash@gnu.org> (permalink)
References	(1 earlier) <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> <ef0aadcc-333d-bb5f-f89c-fbc890f5f99f@case.edu>

Show all headers | View raw

On 7/23/19 11:15 AM, Sam Liddicott wrote:
> 
> 
> On Tue, 23 Jul 2019 at 16:13, Chet Ramey <chet.ramey@case.edu
> <mailto: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?

Right. Isn't that what's happening? The fd got closed in the /bin/echo
process but not in the parent?

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
		 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/

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

Thread

Re: leaks fd for internal functions but not external command Chet Ramey <chet.ramey@case.edu> - 2019-07-23 11:18 -0400

csiph-web