The order in which shell source files are executed depends on whether the shell is interactive or non-interactive, and whether it is a login or non-login shell. Bash and Zsh follow distinct sequences for reading configuration files like .bashrc, .bash_profile, .zshrc, and .zprofile. Understanding this hierarchy is critical for ensuring your environment variables and aliases load correctly across different terminal sessions and scripts.
Bash Login Shell Sequence
When you open a new terminal window or SSH into a server, Bash typically starts as a login shell. This triggers a specific chain of file sourcing designed to set up the initial user environment. The process begins by checking for
/etc/profile, which provides system-wide defaults for all users. Following that, Bash looks for the first existing file among
~/.bash_profile,
~/.bash_login, and
~/.profile. It reads only one of these user-specific files and stops searching further.
If you want to share configuration between login shells and interactive non-login shells, a common pattern is to have
~/.bash_profile explicitly source
~/.bashrc. This ensures that aliases and shell options defined in
.bashrc are available even when starting a fresh login session. Without this explicit step, many users find their custom aliases missing from new terminal windows because
.bashrc is not automatically read during the login phase.
Bash Non-Login Interactive Shell
Non-login interactive shells are often spawned when you run commands inside an existing terminal, use
bash -c, or open a subshell. In this scenario, Bash ignores the login-specific files mentioned above. Instead, it sources
/etc/bash.bashrc if it exists, followed by
~/.bashrc. This distinction is important because changes made only in
.bash_profile will not affect scripts or subshells unless they are also reflected in
.bashrc.
This separation allows administrators to keep system-wide startup logic separate from user-specific interactive settings. However, it can lead to confusion if a user modifies their prompt or sets an alias in
.bash_profile expecting it to work in every context. Always verify where your configurations reside to ensure they apply to the intended shell type. For more complex scripting tasks, understanding these paths helps avoid issues where variables are undefined. You might encounter scenarios similar to those discussed in
Linux RHEL 7 - Shell Script - Can execute command separately but cannot execute inside a script, where execution context matters significantly.
Zsh Login Shell Sequence
Zsh has a more granular approach to initialization files compared to Bash. When starting as a login shell, Zsh reads files in a specific order:
/etc/zsh/zshenv,
~/.zshenv,
/etc/zsh/zprofile,
~/.zprofile,
/etc/zsh/zlogin,
~/.zlogin,
/etc/zsh/zshrc, and finally
~/.zshrc. After the shell is fully initialized and ready for input, it may also read
~/.zlogout upon exit, though this happens after the main sequence.
The key difference lies in the separation of concerns.
.zprofile is used for setting environment variables and paths that should be available to all subsequent processes.
.zshrc is reserved for interactive settings like aliases, functions, and prompt themes. Unlike Bash, Zsh does not rely on a single profile file to bridge the gap; instead, it uses dedicated files for different phases of initialization. This structure reduces conflicts but requires users to understand which file controls what aspect of their environment.
Zsh Non-Login Interactive Shell
For non-login interactive shells, Zsh skips the profile and login files. It still reads
/etc/zsh/zshenv and
~/.zshenv because these are designed to run regardless of shell type. Then, it proceeds directly to
/etc/zsh/zshrc and
~/.zshrc. This means that any configuration placed in
.zprofile will not be applied to subshells or scripts launched from the terminal.
This behavior is intentional to prevent side effects from environment setup interfering with interactive performance. If you need environment variables in subshells, place them in
.zshenv. If you need aliases, keep them in
.zshrc. Mixing these responsibilities can lead to unexpected behavior, such as slow startup times or missing commands. Properly organizing these files ensures a clean and predictable shell experience.
Diagnostics and Troubleshooting
To debug which files are being sourced, you can enable tracing in Bash using
set -x or in Zsh using
setopt XTRACE. This prints each command as it is executed, allowing you to see the exact sequence of file reads. Another useful tool is the
echo $0 command, which displays the name of the current shell instance, helping you determine if it is a login or non-login shell.
If your configurations are not loading, check the permissions of your dotfiles. They must be readable by the user, and sometimes world-readable permissions cause security warnings that prevent sourcing. Additionally, syntax errors in earlier files can halt the sourcing process entirely. Ensure that each file ends cleanly without trailing errors. For issues related to variable expansion in scripts, reviewing how environment variables are handled can provide clarity. See
XDG Base Directory environment variables not respected by notionally compliant software for insights into variable propagation.
Frequently Asked Questions
Why do my aliases disappear in new terminal windows?
Aliases defined only in
.bashrc may not load in login shells if
.bash_profile does not source
.bashrc. To fix this, add a line at the end of
.bash_profile that calls
source ~/.bashrc. This ensures that interactive settings are available in both login and non-login contexts.
What is the difference between .zshrc and .zprofile in Zsh?
.zprofile is sourced during login shell initialization and is ideal for environment variables and PATH modifications.
.zshrc is sourced for every interactive shell and should contain aliases, functions, and prompt configurations. Separating these keeps your environment setup distinct from your interactive experience.
How can I test which shell files are being loaded?
Run
bash -l -x for Bash or
zsh -l -x for Zsh to trace the execution of login shells. For non-login shells, omit the
-l flag. This output shows every file read and command executed, helping you identify missing or conflicting configurations.
Can I use the same file for both Bash and Zsh?
Yes, you can create a shared configuration file and source it from both
.bashrc and
.zshrc. Use conditional checks to ensure compatibility, as some features are shell-specific. This approach reduces duplication and maintains consistency across different shell environments.
Why do environment variables set in .bashrc not appear in scripts?
Scripts typically run in non-interactive, non-login shells that do not source
.bashrc. Variables set here are local to interactive sessions. To make them available to scripts, define them in
.bash_profile or
.profile, which are read by login shells that spawn subprocesses.