[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: /dev/fd/62: No such file or directory
|
From: |
Greg Wooledge |
|
Subject: |
Re: /dev/fd/62: No such file or directory |
|
Date: |
Fri, 28 Mar 2014 08:11:22 -0400 |
|
User-agent: |
Mutt/1.4.2.3i |
On Thu, Mar 27, 2014 at 07:31:31PM -0700, Linda Walsh wrote:
> So whether or not to use /def/fd is a build time option?
On many commerical Unix systems (which don't have /dev/fd/), Bash
falls back to using named pipes.
> 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"...
If your OS vendor's scripts are generating error messages at boot time,
with the version of Bash that the OS vendor shipped, then this is a bug
in those scripts.
If you replaced the version of Bash that the vendor supplied, but did
not change the scripts that may be relying upon the vendor's Bash patches
or version-specific behavior, then the ball is in your own court.