One of the things I found confusing about bash was its startup scripts: there were so many of them. Eventually I snapped and sat down with a terminal and the man pages, and worked out how it actually behaves. Here’s a summary.
|Interactive login||Interactive non-login||Non-interactive||Remote shell|
On startup, bash executes any script labeled A in the table above, followed by the first script B it finds. On exit, it executes any script labeled C above.
Let’s look at the column headings in a little more detail.
An interactive login shell is a shell that you are typing into, that is the first such shell you execute on the machine. Typically you will have had to log in immediately before the shell starts. For example, when you SSH to a remote system and type commands to that system, you are typing into an interactive login shell.
An interactive non-login shell is a new shell started once you have already logged in; one which doesn’t require that you log in again.For example, if you open a new terminal window in your graphical user interface and get a shell prompt, that’s an interactive non-login shell. Another example of an interactive non-login shell would be a sub-shell started from inside a text editor; for example, typing
A non-interactive shell is a shell which doesn’t prompt you; it just runs a program and then exits. The most common example of this is any program written in shell script, such as a
configurescript, a startup script in
/etc/init.d, or any other file marked as executable that has
#!/bin/bashon the first line.
A remote shell is a shell started by a program such as SSH or
rshin order to run a command on a remote machine.For example, the
scpcommands use SSH remote shells in order to copy files between machines.
So looking at the second column, an interactive login shell will execute
/etc/profile always. It then looks for
~/.profile in turn, and executes the first of those it finds. On logout, it executes
/etc/bash.bashrc A† item is special; whether bash searches for it is dependent on a compile-time option.
BASH_ENV is an environment variable which allows you to make non-interactive non-login shells (such as shell scripts) execute a startup script. Set BASH_ENV to the filename of a script and then invoke a sub-shell, and the script will be executed when the sub-shell starts up.
Problems with bash’s behavior
Given the above table, the short summary is:
- If you want something executed only when you first log in, put it in
- If you want something executed only for additional shells (such as OS X terminal windows and xterms), put it in
But there are a couple of problems with this arrangement, problems which suggest that bash’s startup behavior wasn’t really thought out with users in mind.
Firstly, if you are anything like me, most of the things you want to put in shell startup scripts are things you always want executed. Command aliases, for example; or environment variables that tell pieces of software where to find their bits (
You could put those in both
.bash_login, but that represents a maintenance problem: if you change something, you have to remember to change it in both places. So, you might set up a third file for global stuff, and use the shell command
source to read it in from both
.bash_login. I’ve seen some Linux distributions set this up as the default. I don’t like it, however, because it means you now have 3 different startup files floating around, and when you want to change something you have to remember which file it’s in (or sit and work it out).
The second issue with bash startup scripts is that the distinction between login shell and non-login shell isn’t a very useful one these days. Most of us use graphical user interfaces, so we never see a login shell on the machine we’re using. (For example, any terminal window you open on OS X is a non-login one.) Even when I use SSH to shell into a remote system, I don’t generally want that first login to behave differently to any other shell I start (such as shells inside
What I do care about, on the other hand, is whether the shell is interactive. I don’t want my reminder program printing stuff when rsync is trying to connect and transfer files. I don’t want all my custom commands and aliases getting in the way when running scripts to configure or build software. And I don’t want to slow things down loading cdargs unless I’m actually going to be maneuvering around the directory structure by typing.
So what I want is to have a single customization script, and be able to split it into stuff that is always run, and stuff that is only run when I’m using the shell session interactively. Here’s how to do that.
Simple all-purpose bash initialization script
Start off by moving all your current bash startup scripts into a temporary directory, so you have a clean slate. Then, create a skeleton
~/.bashrc that looks like this:
### Start of universal section ### # Commands in this section will be executed by both interactive and # non-interactive shells. # Commands here must produce no output, or they will break commands # like scp and rsync. ### End of universal section ### [ -z "$PS1" ] && return ### Start of interactive section ### # Commands in this section will be executed only by interactive shells. ### End of interactive section ###
cd ~ if you’re not already in your home directory, then
ln -s .bashrc .bash_login
Now you have a single customization file for all your shell sessions, called
~/.bashrc. You can copy in each command from your old customization files, placing them in the appropriate section according to whether you need them all the time, or just in shells that you’re typing in to.
If you really care about login shells
If for some reason you do want to have login shells behave differently from non-login, that’s pretty simple too. Instead of the
ln -s command above, create the following
if [ -f ~/.bashrc ]; then source ~/.bashrc fi # Commands for login shells only go under here
Now you have two places customization commands may be placed, but you get the option of having login-specific stuff.
Dealing with multiple systems
Another trick I use is to examine the host name of the machine. This lets me use the same
.bashrc everywhere; my Mac’s
.bashrc is the same as the one I use on my Linux box and the System z mainframe at work. Here’s the code from the start of
HOST=`hostname -s` if [ "$HOST" = "keynsham" ]; then # Customizations specific to the Mac go in here fi
You can use code like this in either the interactive or non-interactive section of the