Logo
Back

How to permanently set $PATH on Linux/Unix?

To permanently set your $PATH in Linux/Unix, you typically edit a shell configuration file so that every new login session includes the updated path. The exact file to modify depends on your shell and distribution. Below are the most common approaches:

1. Editing Your Shell’s Configuration File

Bash (Most Common)

  1. Open your ~/.bashrc, ~/.bash_profile, or ~/.profile (depending on your distribution and setup).
  2. Add a line similar to: 
    export PATH="$PATH:/path/to/your/directory"
  3. Save and close the file.
  4. Reload the configuration or start a new session: 
    source ~/.bashrc

Which file?

  • ~/.bashrc is read for interactive non-login shells.
  • ~/.bash_profile or ~/.profile is read for login shells.
  • On many distributions, ~/.bash_profile sources ~/.bashrc—so you can place PATH exports in either file.
  • If unsure, check which file is currently sourcing your environment (echo $SHELL or consult distro documentation).

Zsh

For Z shell, edit ~/.zshrc:

export PATH="$PATH:/path/to/your/directory"

Then:

source ~/.zshrc

Fish Shell

Fish shell uses a different syntax. For a permanent path change:

set -Ux PATH /path/to/your/directory $PATH

This creates a universal variable that persists across sessions.

2. System-Wide Settings

If you want every user on the system to have the same updated PATH:

  1. Edit a file like /etc/profile, /etc/bash.bashrc, or a script inside /etc/profile.d/.
  2. Add a line: 
    export PATH="$PATH:/path/to/your/directory"
  3. Save the file.
  4. Have users re-login to apply the change system-wide.

Be cautious with system-wide changes—only do this if you’re sure all users need the updated path.

3. Verifying the Changes

After updating and reloading, confirm your new path is active:

echo $PATH

You should see :/path/to/your/directory at the end (or wherever you placed it).

4. Troubleshooting

  1. Override by Another File: If your changes aren’t taking effect, you might have a shell that reads a different config file. Check whether you’re in Bash, Zsh, etc.
  2. Export Placement: Ensure the export PATH=... line isn’t placed inside a conditional block that might not always run.
  3. Local vs. Remote: If you’re using SSH, check whether your remote login environment sources the same files as a local session.

Further Learning

For more depth on shell usage and to hone your broader coding skills, these two courses from DesignGurus.io can help:

  1. Grokking Data Structures & Algorithms for Coding Interviews
    Learn fundamental data structures and algorithms, improving efficiency in scripts and software projects.

  2. Grokking the Coding Interview: Patterns for Coding Questions
    Master the major coding patterns tested at top tech interviews, helping you tackle complex problems more effectively.

By maintaining a well-organized, permanent $PATH and strengthening your coding fundamentals, you’ll significantly boost productivity and capability in Linux/Unix environments.

CONTRIBUTOR
TechGrind