> Where should PATH, CLASSPATH, LD_LIBRARY_PATH and other such environment
> definitions be defined? Should they live in .profile or .kshrc? And why?
.profile (except for LD_LIBRARY_PATH which should be ruthlessly
destroyed if you have any control over the applications that need it -
if you have no control, put it in .profile anyway). Why? Because .kshrc
is read everytime you run a command so it will be needlessly actioned
again and again. Furthermore, setting the PATH in .kshrc can make
tracking down problems in tools that try and invoke applications really
tricky ... you do a 'echo $PATH' and everything is fine but the tool
says it cannot find 'such and such application' in that PATH.
I'm not really here - it's just your warped imagination.