Hello, I often update the environmental variables (such as PATH, CLASSPATH, JAVA_HOME, TOMCAT_HOME, etc.) in my .profile when I install new software. But in order for the new values to take effect, I log out of my x session (gnome in my case), and then log back in. Is there any way for the new values of environmental variables to take effect without logging out and back in? Thanks very much. Dom
On Saturday 23 October 2004 4:29 pm, Dom Incollingo wrote:
I often update the environmental variables (such as PATH, CLASSPATH, JAVA_HOME, TOMCAT_HOME, etc.) in my .profile when I install new software. But in order for the new values to take effect, I log out of my x session (gnome in my case), and then log back in. Is there any way for the new values of environmental variables to take effect without logging out and back in? Thanks very much.
it used to be: prompt:> . .profile as in dot space dot-profile -- Paul Cartwright Registered Linux user # 367800
Paul Cartwright writes:
On Saturday 23 October 2004 4:29 pm, Dom Incollingo wrote:
I often update the environmental variables (such as PATH, CLASSPATH, JAVA_HOME, TOMCAT_HOME, etc.) in my .profile when I install new software. =A0But in order for the new values to take effect, I log out of my x session (gnome in my case), and then log back in. =A0Is there any way for the new values of environmental variables to take effect without logging out and back in? =A0Thanks very much.
it used to be: prompt:> . .profile =20
as in dot space dot-profile
That works only for the shell that you have running in a terminal window (e.g., konsole), but kde startup script running "in the background" still has the old environment. Unfortunately, there is no way to refresh that without a re-login. -Ti -- Ti Kan http://www.amb.org/ti Vorsprung durch Technik
Ti Kan wrote:
Paul Cartwright writes:
On Saturday 23 October 2004 4:29 pm, Dom Incollingo wrote:
I often update the environmental variables (such as PATH, CLASSPATH, JAVA_HOME, TOMCAT_HOME, etc.) in my .profile when I install new software. =A0But in order for the new values to take effect, I log out of my x session (gnome in my case), and then log back in. =A0Is there any way for the new values of environmental variables to take effect without logging out and back in? =A0Thanks very much.
it used to be: prompt:> . .profile =20
as in dot space dot-profile
That works only for the shell that you have running in a terminal window (e.g., konsole), but kde startup script running "in the background" still has the old environment. Unfortunately, there is no way to refresh that without a re-login.
-Ti
Thanks very much for the replies. Before I read the second reply, I tried the . .profile, and, as you stated, it worked fine for the konsole session but not for the entire gnome environment. I'll continue to do a re-login in the future. Thanks again for your help. Dom
On Saturday 23 October 2004 5:01 pm, Ti Kan wrote:
That works only for the shell that you have running in a terminal window (e.g., konsole), but kde startup script running "in the background" still has the old environment. Unfortunately, there is no way to refresh that without a re-login.
geez, I keep forgetting this is now an X environment, never used to be that way :) how about /opt/kde3/bin/startkde ?? looks like you are right, not without a relogin. -- Paul Cartwright Registered Linux user # 367800
On Saturday 23 October 2004 03:29 pm, Dom Incollingo wrote:
Is there any way for the new values of environmental variables to take effect without logging out and back in? Thanks very much.
Dom
run: source ~/.profile ? This will only be valid in your current xterm. If you use lots of tabbed konsoles like me, you can select the option to send the input to all consoles first. Be sure to uncheck it after you've broadcast your command. -- Stephen If your desktop gets out of control easily, you probably have too much stuff on it that doesn't need to be there. Donna Smallin, "Unclutter Your Home"
Stephen, On Sunday 24 October 2004 07:43, Stephen Boulet wrote:
...
? This will only be valid in your current xterm.
If you use lots of tabbed konsoles like me, you can select the option to send the input to all consoles first. Be sure to uncheck it after you've broadcast your command.
Thanks for that tip. It's too bad you can't get to that command unless the menu bar is shown. In fact, it's rather odd that there are _any_ commands that cannot be reached via the context menu and require the user to display the menu bar first.
--
Stephen
Randall Schulz
On Sunday 24 Oct 2004 17:07, Randall R Schulz wrote:
Stephen,
On Sunday 24 October 2004 07:43, Stephen Boulet wrote:
...
? This will only be valid in your current xterm.
If you use lots of tabbed konsoles like me, you can select the option to send the input to all consoles first. Be sure to uncheck it after you've broadcast your command.
Thanks for that tip.
It's too bad you can't get to that command unless the menu bar is shown. In fact, it's rather odd that there are _any_ commands that cannot be reached via the context menu and require the user to display the menu bar first.
--
Stephen
Randall Schulz
not everyone wants the screen full of menus at every touch of the mouse. -- Linux user No: 256242 Machine No: 139931 G6NJR Pete also MSA registered "Quinton 11" A Linux Only area Happy bug hunting M$ clan, The time is here to FORGET that M$ Corp ever existed the world does not NEED M$ Corp the world has NO USE for M$ Corp it is time to END M$ Corp , Play time is over folks time for action approaches at an alarming pace the death knell for M$ Copr has been sounded . Termination time is around the corner ..
participants (6)
-
Dom Incollingo -
Paul Cartwright -
peter Nikolic -
Randall R Schulz -
Stephen Boulet -
ti＠amb.org