Shell Script source file not saved

Question

I saved a shell script in bin(created by me). When I run the program, to avoid ./ to run the script I need to copy the script to one of the directories specified by PATH variable. The bin directory created is not in the path list. So, to add to the PATH list:

export PATH=~/bin:"$PATH"

But this directory is not getting saved to the PATH list. When I open a new terminal window I need to export it again to run the script. How can I add it to PATH list permanently? Also if I try to move the script to the present PATH listed directory, it says PERMISSION DENIED. Do I have to move it by becoming a root user?

Answer 1

You can add export PATH=~/bin:"$PATH" to your ~/.profile file. Add it to the bottom, save then reconnect to SSH.

Alternatively, if you want this change to be system wide for any user, you can edit the path in /etc/environment.

Answer 2

This one worked for me.

Open your .bashrc gedit ~/.bashrc

The text editor is opened.

if [ -d "$HOME/bin" ] ; then
    PATH="$HOME/bin:$PATH"
fi

Paste this and edit the .bashrc. After closing the text editor, source ~/.bashrc

If you get Permission denied, it means the script is not in executable format. chmod 755 program_name This should do the work. Open the new Terminal and it will work.

Answer 3

Add custom home dir path to $PATH

1. Edit your ~/.profile

2. Add this line after all $PATH related vars:

   export PATH="$PATH:$HOME/your-home-dir-path"

3. Save file.

4. Log out / Restart.

Adding this to your ~/.profile enable this change to terminal and text-mode.

Just in case your custom path is ~/bin or ~/.local/bin !!!

As already said in question comment, these locations are already included in PATH in Ubuntu!

You can just:

1. Create the directory (e.g., ~/bin).
2. Copy your script to it.

3. Change its permitions to be executable with the command:

   chmod +x ~/bin/script.sh

4. Logout / login. Alternatively, you can execute source ~/.profile

Answer 4

As already mentioned, your ~/.profile should already contain something like the following:

# set PATH so it includes user's private bin if it exists
if [ -d "$HOME/bin" ] ; then
    PATH="$HOME/bin:$PATH"
fi

However, it sounds like you are launching an interactive non-login bash shell (i.e. you are not connecting over ssh but launching a terminal from a desktop environment) which does not read ~/.profile and instead ~/.bashrc is read as explained here.

You can modify ~/.bashrc to add the path or read ~/.profile for non-login shells as explained here but as Jacob mentioned if you logout/login this is not required.

To understand the difference between login and non-login shell see this answer.

Answer 5

When you run

export PATH=~/bin:"$PATH"

you are setting the PATH environment variable and exporting it to the running parent terminals. It's like saying "the new PATH variable is this, spread the word". It works, but once you restart your computer the PATH will go back to the configured one. To make the change permanent, you will have to edit the .profile file on your home folder. It usually has this:

    # set PATH so it includes user's private bin if it exists
    if [ -d "$HOME/bin" ] ; then
        PATH="$HOME/bin:$PATH"
    fi

which would include the $HOME/bin folder automatically if it exists. But if it doesn't you can just add either the commands above, or:

    export PATH="$PATH:$HOME/bin"

to the file and this folder will be included in the PATH on every session of your user.

You need root permissions to write in the /usr/bin directory, but that's not necessary if you change the .profile file.