>> Nathan Scott <nathans@xxxxxxxxxxxxxxxxxxxxxxxx> writes:
> > > 002: [: 2 : integer expression expected
> > > 002: [: 3 : integer expression expected
>
> can you send me the output from "sh -x 002"? - looks like
> the lstat64 output/filtering is off with the pixies.
This is the bash related bug I reported a while ago (I do remember
seeing it commited to the CVS tree)
Index: cmd/xfs/stress/002
===================================================================
RCS file: /cvs/linux-2.4-xfs/cmd/xfs/stress/002,v
retrieving revision 1.5
diff -u -r1.5 002
--- cmd/xfs/stress/002 2000/10/31 22:12:46 1.5
+++ cmd/xfs/stress/002 2000/11/10 08:34:40
@@ -64,7 +64,7 @@
do
ln $TEST_DIR/$tmp.1 $TEST_DIR/$tmp.$l
x=`src/lstat64 $TEST_DIR/$tmp.1 | sed -n -e '/ Links: /s/.*Links: *//p'`
- if [ "$l" -ne "$x" ]
+ if [ "$l" -ne $x ]
then
echo "Arrgh, created link #$l and lstat64 looks like ..."
src/lstat64 $TEST_DIR/$tmp.1
The problem is a POSIX sh doesn't care about the whitespace inside "$x"
(something like "2 ") but bash (as /bin/sh) does. At this point $x is
not empty, if it is, something else went bonkers.
--
Marcelo
|