Recently I was working on an issue where an application was not retaining the umask setting set in the root users profile or
/etc/profile. After looking into the issue a bit it seemed that the application in question only applied the umask setting that was set in
/etc/bashrc and would not even accept the values being the applications own start scripts.
After doing a bit of researched I learned a little bit more about what exactly these files do, the differences between them and when they are executed. I figured this would be a good thing to share as it is not a topic that comes up very often.
What is /etc/profile used for?
If you have been using Linux for a while you are probably familiar with the
.bash_profile files in your home directory. These files are used to set environmental items for a users shell. Items such as umask, and variables such as
/etc/profile file is not very different however it is used to set system wide environmental variables on users shells. The variables are sometimes the same ones that are in the
.bash_profile, however this file is used to set an initial
PS1 for all shell users of the system.
In addition to the setting environmental items the
/etc/profile will execute the scripts within
/etc/profile.d/*.sh. If you plan on setting your own system wide environmental variables it is recommended to place your configuration in a shell script within
What is /etc/bashrc used for?
.bash_profile you will also commonly see a .bashrc file in your home directory. This file is meant for setting command aliases and functions used by bash shell users.
Just like the
/etc/profile is the system wide version of
/etc/bashrc for Red Hat and
/etc/bash.bashrc in Ubuntu is the system wide version of
Interestingly enough in the Red Hat implementation the
/etc/bashrc also executes the shell scripts within
/etc/profile.d but only if the users shell is a Interactive Shell (aka Login Shell)
When are these files used?
The difference between when these two files are executed are dependent on the type of login being performed. In Linux you can have two types of login shells, Interactive Shells and Non-Interactive Shells. An Interactive shell is used where a user can interact with the shell, i.e. your typical bash prompt. Whereas a non-Interactive shell is used when a user cannot interact with the shell, i.e. a bash scripts execution.
The difference is simple, the
/etc/profile is executed only for interactive shells and the
/etc/bashrc is executed for both interactive and non-interactive shells. In fact in Ubuntu the
/etc/profile calls the
Interactive Shell vs Non-Interactive Shell
To show an example of an interactive shell vs a non-interactive shell I will add a variable into both
/etc/bash.bashrc on my Ubuntu system.
# grep TEST /etc/profile export TESTPROFILE=1
# grep TEST /etc/bash.bashrc export TESTBASHRC=1
The below example is showing an interactive shell, in this case both the
/etc/bash.bashrc was executed.
# su - # env | grep TEST TESTBASHRC=1 TESTPROFILE=1
In this example we are running a command through SSH that is non-interactive; because this is a non-interactive shell only the
/etc/bash.bashrc file is executed.
# ssh localhost "env | grep TEST" [email protected]'s password: TESTBASHRC=1
In my case the applications child processes are not recognizing the umask value set in
/etc/profile but do recognize the value in
/etc/bashrc. This tells me that the subprocess is starting as a non-interactive shell. While the suggested route of modifying environmental variables is to add a shell script into
/etc/profile.d in my case it is better to set the umask value in the
Recently Benjamin published his first book; Red Hat Enterprise Linux Troubleshooting Guide. In addition to writing, he has several Open Source projects focused on making Ops easier. These projects include Automatron, a project enabling auto-healing infrastructure for the masses.
Identify, capture and resolve common issues faced by Red Hat Enterprise Linux administrators using best practices and advanced troubleshooting techniques
What people are saying:
Excellent, excellent resource for practical guidance on how to troubleshoot a wide variety of problems on Red Hat Linux. I particularly enjoyed how the author made sure to provide solid background and practical examples. I have a lot of experience on Red Hat but still came away with some great practical tools to add to my toolkit. - Amazon Review