[Chapter 2] 2.6 Use Absolute Pathnames in Shell Setup Files
Author: Jerry Peek, Tim O'Reilly & Mike Loukides
Date: 1998-08-04T21:32:03Z

#

| Chapter 2 Logging In |

## 2.6 Use Absolute Pathnames in Shell Setup Files

One common mistake in shell setup files (2.2) is lines like these:

    `...`
    source .aliases
    echo "Logged in at `date`" >> login.log

What's wrong with those lines? Both use relative pathnames (1.21) for the files (.aliases, login.log), assuming the files are in the home directory. Those lines won't work when you start a subshell (38.4) from somewhere besides your home directory, because your files .cshrc or ENV (like .kshrc) are read whenever a shell starts. If you ever use the source or `.` commands (44.23) to read the .profile and .login from outside your home directory, you'll have the same problem.

Use absolute pathnames instead. As article 14.11 explains, the pathname of your home directory is in the tilde (`~`) operator or the `$HOME` or `$LOGDIR` environment variable:

>     source ~/.aliases
>     echo "Logged in at `date`" >> ~/login.log

- JP

2.5 Tips for Speeding up Slow Logins |  | 2.7 C Shell Setup Files Aren't Read When You Want Them to Be?