Linux Shell Environment Path: Difference between revisions

From Free Knowledge Base- The DUCK Project
Jump to navigation Jump to search
Created page with "Need to add a directory path to the shell path statement for your own scripts? * Per user shell vi ~/.profile Look for the line with a comment about "set PATH so it includes ..."
 
mNo edit summary
Line 1: Line 1:
The current path environmental variable can be viewed
echo $PATH
capital letters on PATH.  Want to know if a command is in $PATH?
which command
Need to add a directory path to the shell path statement for your own scripts?
Need to add a directory path to the shell path statement for your own scripts?
* Per user shell
* Per user shell

Revision as of 11:32, 3 June 2019

The current path environmental variable can be viewed

echo $PATH

capital letters on PATH. Want to know if a command is in $PATH?

which command

Need to add a directory path to the shell path statement for your own scripts?

  • Per user shell
vi ~/.profile

Look for the line with a comment about "set PATH so it includes user's private bin directories" and add your custom path in there like this: ( added /myscripts to the path )

PATH="$HOME/bin:$HOME/.local/bin:/myscripts:$PATH"

note: In the past we used ~/.bash_profile and had to include "export PATH"

Look at /etc/profile which is used for each new user directory created. It has a script still looking for .bash_profile so it appears that if a .bash_profile is created, the script will identify its existence and use it.

Also note that .bashrc is executed every time a bash shell is opened and .bash_profile only if it's a login shell. Also, it appears that the default profile still looks for