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-25 10:11 -0400
Message-ID	<mailman.2209.1564063890.2688.bug-bash@gnu.org> (permalink)
References	(12 earlier) <7a33daac-16ba-b98a-54ca-e005fd8b041e@case.edu> <CAOj-5WD0jLQN4eX=gf+wqjRAz4YHVw_9wr747-Gh3dsOkNhXjQ@mail.gmail.com> <8761ae1a-f51c-e468-0a32-3447bfa7f287@case.edu> <CAOj-5WBJA_nxhQ=_Y7307darqs2L55mZqCCU8YOvwN64YwkFGQ@mail.gmail.com> <91868af9-f8a6-bbe2-2983-187683ab5a87@case.edu>

Show all headers | View raw

On 7/25/19 9:03 AM, Sam Liddicott wrote:

> Perhaps if the named fd is also closed on the same statement that opened
> it, it could be kept closed rather than saved and re-opened.
> Being closed at the same statement is a strong indicator that it was only
> used to aid fd transplants. Why keep open what the author closed?

That's an interesting suggestion. I considered it at some point, and
there's even a comment in the code about it. I'll look at it again.

Chet

-- 
``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-25 10:11 -0400

csiph-web