|
From: | Yuri |
Subject: | Re: bash leaks sh-np-NNN files and pipes in /tmp/ when command substitution is used |
Date: | Thu, 12 Dec 2013 09:57:21 -0800 |
User-agent: | Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 |
On 12/12/2013 05:02, Greg Wooledge wrote:
If bash is using named pipes of the form /var/tmp/sh-np-* or /tmp/sh-np-* then the compile-time options or detection must have failed to find a usable/dev/fd/ subsystem. (My HP-UX workstation is littered with sh-np-* FIFOs in BOTH /tmp and /var/tmp.)
BSDs traditionally opposed to /dev/fd and /proc file systems. bash configure specifically tests for /dev/fd/3 and notes this is to detect FreeBSD, which only implements /dev/fd/{0..2}.
I also have a lot of /tmp/sh-np-*. bash leaves them when race condition doesn't occur. And when it occurs, oddly, this is because the premature deletion of /tmp/sh-np-*
If they would keep those fifos in deleted state as much of the time as possible, such leak would be minimal.
Yuri
[Prev in Thread] | Current Thread | [Next in Thread] |