Re: /dev/fd/62: No such file or directory

[Linda Walsh]

Chet Ramey wrote:
> On 3/27/14, 8:42 PM, Linda Walsh wrote:
>
> > I certainly wouldn't be against a builtin that would return
> > the same thing as /dev/fd/62 -- just one that doesn't try to
> > walk an external path to perform internal functions (have looked
> > several times at scripts that have shown such messages, and
> > have yet to see any mention of /dev/fd/xx in the script, so I'm
> > /presuming/ (sigh) that it is something internal to bash?
>
> Process substitution, whose entire reason for existence is to turn a
> (pipe) file descriptor into a filename.  If you want to use process
> substitution in a context where /dev/fd might not be available, make
> sure you don't tell bash to use it at build time or use another
> scripting technique.
>
>  
----
        So whether or not to use /def/fd is a build time option?

        It's a minority of scripts but have noticed the message
in some startup scripts.  It's not just my scripts but vendor scripts
as well.  I'll have to find out why.. but it seems like it a
"gotcha"...