I have a really odd bash error which I can't diagnose at all at the moment.
It refuses to run any script in the current directory when running as bash. If I run sh instead it works.
E.g. I have a script called 'build' in /home/chris/ikiwiki
Whether or not it has #!/bin/bash at the top of it then when I enter 'build' I get the error:-
bash: ./build: No such file or directory
However if I put #!/bin/sh at the top of the script (or if I run sh) then it runs without problems.
Ah, I have a clue, it seems as if bash doesn't want to run scripts which are in the current directory even though . is on my path. Is there some sort of clever security flag in bash that prevents this?
If a script is in (for example) /home/chris/bin (which is on my path) it runs OK with a #!/bin/bash at the top, however if the script is in the current directory I get the error even though . is on my path.
Wierd! Does anyone have any ideas what might be wrong? I'm sure it didn't used to be like this.