Test -f Behaves Oddly After Cd Command

[clofland]

Write this script:

cd /bin
if (test -f joe);then echo yes1;fi
if (test -f joe);then echo yes2;fi

and run it. (You can use any dir, it doesn't have to be /bin)

There is NO file called "joe" in my /bin directory, but I always get "yes1" but not "yes2"

Is this some known bash or Linux issue where you always get a false possitive on a test -f after you do a cd command?

This causes some of the built in scripts like /etc/ppp/ppp-off to throw out errors sometimes.

[pgas]

hmm, interesting.

If I place your script on a partition of the internal flash (/ or /home) , it doesn't work correctly.

If I place the same script on my ext3 formatted or on a nfs mount, it works correctly.

if you drop the parentheses it works correctly everywhere.

I tried with "test" from coreutils instead of the "test" from busybox, with the same results.

somehow jffs2 seems to cause problems, i don't have an explanation

[inode0]

Write this script:

cd /bin
if (test -f joe);then echo yes1;fi
if (test -f joe);then echo yes2;fi

and run it. (You can use any dir, it doesn't have to be /bin)

There is NO file called "joe" in my /bin directory, but I always get "yes1" but not "yes2"

Is this some known bash or Linux issue where you always get a false possitive on a test -f after you do a cd command?

Just tested on my 6k and I don't see this bizarre behavior. Nothing is printed from either if statement as one would expect.

John