Getting “command not found” error in bash script

Question

I have written a bash script that gets three paths based on input parameters and then then gets the imagename/filename in the path.

Something like:
I provide:

Answer 1

$PATH is a predefined variable which gives the directories to search when looking for executables. Pick a different variable name for your script and you'll be fine.

Answer 2

You are using the PATH that is special and used to locate the commands and that is why ls can't be resolved. Use any name other than PATH

if [ $CC = "n" ] ; then  
    MY_PATH=$PATH1  
elif [ $CC = "k" ] ; then  
    MY_PATH=$PATH2  
else  
    MY_PATH=$PATH3  
fi 

export MY_PATH

IMG="`ls $MY_PATH | cut -d "/" -f6`"

Answer 3

I had this problem, turns out editing a bash script using Notepad++ was adding DOS line endings instead of UNIX line endings. Running the script in a Linux environment was causing the 'command not found' error to be thrown.

Managed to diagnose the problem by running my script like so:

bash -x testscript.sh

Which will dump any compiler output. The error message that gets thrown is:

bash -x testscript.sh
+ $'\r'
: command not found 2:
'estscript.sh: line 3: syntax error near unexpected token `{

I fixed the issue by changing the formatting of line endings in Notepad++ to be UNIX not DOS by going Edit -> EOL Conversion -> UNIX.

Answer 4

Use a different variable name than PATH. $PATH is the environment variable which tells your shell where to look for executables (so, e.g., you can run ls instead of /bin/ls).

Answer 5

The problem is that you are redefining the PATH variable where bash looks into to find the binary files if you don't use a complete path when calling.

You should change the PATH in your bash script to MYPATH or something like that, so that it doesn't mess with the already environmental variables.

If you don't know what the PATH variable is for you can look at wikipedia's article

Answer 6

$PATH is a special environment variable that contains a list of directories where your shell (in this case, bash) should look in when you type a command (such as find and ls.) Just try echo $PATH in a script or in a shell to get a feeling of what it looks like (you will typically have /bin, /usr/bin and /usr/local/bin listed there, maybe more.)

As you don't really need to redefine this variable in this particular script, you should use another name than $PATH.