I'm trying to execute a bash script (git-ftp) but I can't seem to do it. This is what happens:
[trusktr@rocketship ~]$ ~/scripts/git-ftp
: No such file or directory
The file has permissions 755.
This is the contents of the script: http://pastie.org/3567556
Why am I getting this error? What can I do to fix the problem?
I have seen this error if the script has windows line endings instead of unix line endings. Try running dos2unix on the script and see if you get the same error.
"\r" The leading carriage return disappears when printed since on your Unix terminal it just moves the cursor to column 0.
#!/usr/bin/env bash\r, so env prints the error "env: bash\r: No such file or directory". The carriage return makes the second part (": No such file or directory") overwrite the first part, so you don't see the first part. (p.s.: well spotted, joesdiner.)Is there a #! (hash bang) line in the script, and does the pathname resolve?
If the script is running, it may be something in the script. Add this command to the top of the script, before any other command (but of course after the hash bang, if there is one):
set -x # enable trace mode
set -x but nothing new happens.
bash -x ~/scripts/git-ftp and see if that reveals anything. FWIW the script runs fine for me printing the usage messageAs joesdiner and Gordon Davisson point out, the error is likely happening because the script starts with an env shebang that ends with a CR/LF line terminator, e.g. #!/usr/bin/env bash\r\n
When the script is executed, something like /usr/bin/env $'bash\r' ~/scripts/git-ftp is actually run. A program called bash\r (with a CR character at the end) is - hopefully! - unlikely to be found, and env will print:
env: bash\r: No such file or directory
But the \r will send the cursor back to the start of the line, and the env: bash text will be overwritten by what follows, i.e.:
: No such file or directory
Some versions of env will at least be decent enough to escape the literal \r:
env: ‘bash\r’: No such file or directory
But either way, it will first look for a bash\r executable in the path and try to execute it.
This is arguably a dangerous thing for env to do, since it raises the possibility of someone adding a bash\r executable somewhere in the user's path.
ls ~/scripts/git-ftpwork?