Package: bash
Version: 3.2-4
Severity: normal
In some cases, the noclobber option's error output substitutes a file
descriptor for a file name. Please compare the file name field in the
output of the following examples.
The file "bar" in the current directory exists.
Test A:
Code:
#!/bin/bash
set -o noclobber
true
echo foo > bar
Output:
$ ./test
./test: line 5: bar: cannot overwrite existing file
Test B:
Code:
#!/bin/bash
set -o noclobber
true | true
echo foo > bar
Output:
[EMAIL PROTECTED]:~$ ./test
./test: line 5: 1: cannot overwrite existing file
Test C:
Code:
#!/bin/bash
set -o noclobber
true | true
echo foo 1> bar
Output:
$ ./test
./test: line 5: bar: cannot overwrite existing file
Note: Test B adds "| true" to the second statement; Test C adds "1" to
the third statement.
Test D (interactive):
$ set -o noclobber
$ true ; echo foo > bar
bash: bar: cannot overwrite existing file
$ true | true ; echo foo > bar
bash: 1: cannot overwrite existing file
$ true | true ; echo foo 1> bar
bash: 1: cannot overwrite existing file
$ true | true ; echo foo 2> bar
bash: 2: cannot overwrite existing file
Note: the change in the file descriptor changes the error message only
in the interactive test.
All test cases are equivalent and should return the same error message.
Thanks,
-Dave
--
David A. Harding Website: http://dtrt.org/
1 (609) 997-0765 Email: [EMAIL PROTECTED]
Jabber/XMPP: [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
