Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #15244 > unrolled thread
| Started by | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| First post | 2019-07-25 10:11 -0400 |
| Last post | 2019-07-25 10:11 -0400 |
| Articles | 1 — 1 participant |
Back to article view | Back to gnu.bash.bug
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: leaks fd for internal functions but not external command Chet Ramey <chet.ramey@case.edu> - 2019-07-25 10:11 -0400
| From | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| Date | 2019-07-25 10:11 -0400 |
| Subject | Re: leaks fd for internal functions but not external command |
| Message-ID | <mailman.2209.1564063890.2688.bug-bash@gnu.org> |
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 top | Article view | gnu.bash.bug
csiph-web