NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
corepuncher, Putting user-specific definitions into the system-wide profile-file subjects all users on the system to those definitions regardless of their relevancy; consequently, it is not recommended. Conventionally, environment variable definitions are put into the user's profile-file (e.g., "~/.bash_profile"), the profile-file includes the runtime-configuration file (e.g., "~/.bashrc"), and the runtime-configuration file includes the system runtime-configuration file (e.g., "/etc/bashrc"). > hmm.. > > if I do this with SINGLE quotes: > > root@SERVER:~# su - ldm -c 'echo $SHELL; echo $PATH' > /bin/bash > /home/ldm/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games > > but with double quotes: > > root@SERVER:~# su - ldm -c "echo $SHELL; echo $PATH" > /bin/bash > /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/home/gempak/NAWIPS/os/linux64/bin:/home/gempak/NAWIPS/bin:/home/ldm/decoders:/home/ldm/util:/home/ldm/bin > > Then the commands as "ldm": > > ldm@SERVER:~$ echo $SHELL > /bin/bash > ldm@SERVER:~$ echo $PATH > /home/ldm/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/home/gempak/NAWIPS/os/linux64/bin:/home/gempak/NAWIPS/bin:/home/ldm/decoders:/home/ldm/util:/home/ldm/bin > > I added the ldm path stuff to Gemenviron.profile. I thought that would take > care of it all, but maybe not. I source Gemenviron.profile in > /etc/bash.bashrc. Perhaps I need to also place it in /etc/profile? > > > FIXED !!! > > I put this back in /home/ldm/.profile: > > . /home/gempak/NAWIPS/Gemenviron.profile > > Somehow, that fixed it. Which confuses me, b/c I also source this line in > /etc/bash.bashrc, which I thought applied to "every" user. Regards, Steve Emmerson Ticket Details =================== Ticket ID: NYK-599005 Department: Support LDM Priority: Normal Status: Closed