> > i just installed 4.6-RELEASE, and notice that > > the '2>&-' sh (FBSD) construct seems to be broken. > > i am going thru all my scripts having to change > > it to /dev/null ...
> In what way is it broken? > If the construct is generally used for hiding errormessages, one > should probably replace it with '2>/dev/null' anyway, since 2>&- > only closes filedescriptor 2 at startup of program and the first file > the program opens will be assigned the very same and all output > to stderr will come up in that file. > Example, > sh> tee < /dev/null 2>&- empty /nonexistent/missingfile > sh> cat empty > tee: /nonexistent/missingfile: No such file or directory > sh> this example above is incorrect with regards to 4.6-RELEASE. with 4.6-RELEASE, output is as follows: Example, sh> tee < /dev/null 2>&- empty /nonexistent/missingfile tee: /nonexistent/missingfile: No such file or directory sh> cat empty sh> > sh> tee < /dev/null 2>/dev/null empty /nonexistent/missingfile > sh> cat empty > sh> > > i figure it's not realistic to assume a bug this > > obvious would make it to release stage, so my > > question is - is something else going on? > > or is this just due to changes in 'sh'? > > is it a bug? or is it a permenent change? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
