$PATH question

[Romeo Theriault]

On 8/1/07, Johan Booysen <johan at matrix-data.co.uk> wrote:
>
> Hi,
>
> I've set up persistent VNC sessions for some of our developers on a
> RHEL3 server.  They now tell me that when they access their VNC
> sessions, then /usr/local/bin does not appear in their path.  A bit of
> testing seems to indicate that manually killing the VNC session and
> creating a new one "updates" the path to include /usr/local/bin.
>
> Does anyone know where /usr/local/bin actually gets added to $PATH in
> the first place?  We set some environment variables via scripts in
> /etc/profile.d, but I can't seem to find where /usr/local/bin gets added
> to the path.
>
> Probably a silly question and/or me having a daft moment here...
>
> Thanks.
>
> Johan
>
> --
> redhat-list mailing list
> unsubscribe mailto:redhat-list-request at redhat.com?subject=unsubscribe
> https://www.redhat.com/mailman/listinfo/redhat-list
>

What follows is from the bash man page, hope it helps.


 When bash is invoked as an interactive login shell, or as a non-interactive
shell with the --login option, it first reads and  executes  commands
       from  the  file /etc/profile, if that file exists.  After reading
that file, it looks for ~/.bash_profile, ~/.bash_login, and ~/.profile, in
that
       order, and reads and executes commands from the first one that exists
and is readable.  The --noprofile option may be  used  when  the  shell  is
       started to inhibit this behavior.

       When a login shell exits, bash reads and executes commands from the
file ~/.bash_logout, if it exists.

       When  an  interactive  shell that is not a login shell is started,
bash reads and executes commands from /etc/bash.bashrc and ~/.bashrc, if
these
       files exist.  This may be inhibited by using the --norc option.  The
--rcfile file option will force bash to read and execute commands from  file
       instead of /etc/bash.bashrc and ~/.bashrc.

       When  bash  is  started non-interactively, to run a shell script, for
example, it looks for the variable BASH_ENV in the environment, expands its
       value if it appears there, and uses the expanded value as the name of
a file to read and execute.  Bash behaves as if the following command  were
       executed:
              if [ -n "$BASH_ENV" ]; then . "$BASH_ENV"; fi
       but the value of the PATH variable is not used to search for the file
name.


-- 
Romeo Theriault
System Administrator
University of Maine at Fort Kent
Ph#: 207-834-7815
Em@: romeo.theriault at maine.edu