[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Leak in BASH "named" file descriptors?
From: |
Reuti |
Subject: |
Re: Leak in BASH "named" file descriptors? |
Date: |
Fri, 29 Jan 2016 00:56:26 +0100 |
Hi,
Am 28.01.2016 um 23:25 schrieb Andreas Schwab:
> Mathieu Patenaude <mpatenaude@gmail.com> writes:
>
>> The issue I see with relying on the bash EXIT to actually have the system
>> do the cleanup is when you have a script that does things in a forever
>> loop, you end up with FD exhaustion when using "named" FD and here strings.
>
> Of course, if you don't close (or reuse) your descriptors you will run
> out of them eventually.
The man page of bash 4.2 says about REDIRECTION: In this case [...] the shell
will allocate a file descriptor greater than 10 and assign it to varname.
While looking into this discussion, I get 10 as first varname assigned in this
way. Either a bug in bash or the man page?
-- Reuti
>
> Andreas.
>
> --
> Andreas Schwab, schwab@linux-m68k.org
> GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
> "And now for something completely different."
>
- Leak in BASH "named" file descriptors?, Mathieu Patenaude, 2016/01/27
- Re: Leak in BASH "named" file descriptors?, Greg Wooledge, 2016/01/28
- Re: Leak in BASH "named" file descriptors?, Andreas Schwab, 2016/01/28
- Re: Leak in BASH "named" file descriptors?, Mathieu Patenaude, 2016/01/28
- Re: Leak in BASH "named" file descriptors?, Greg Wooledge, 2016/01/28
- Re: Leak in BASH "named" file descriptors?, Mathieu Patenaude, 2016/01/28
- Re: Leak in BASH "named" file descriptors?, Andreas Schwab, 2016/01/28
- Re: Leak in BASH "named" file descriptors?,
Reuti <=
- Re: Leak in BASH "named" file descriptors?, Chet Ramey, 2016/01/28
- Re: Leak in BASH "named" file descriptors?, Mathieu Patenaude, 2016/01/28
Re: Leak in BASH "named" file descriptors?, Chet Ramey, 2016/01/28