Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

/etc/environment is officially the correct place for system wide environment variables. But how can I reload the assignments in this file without rebooting or relogging?

Interestingly enough google does not help me here, aside from the dozens of blog posts suggesting to use

source /etc/environment

which obviously will never work because /etc/environment is a list of assigments (one per line) and not an executable script (hence the missing export commands in /etc/environment ...).

share|improve this question
6  
Systemwide, I have no idea. For the current shell session, you can use for line in $( cat /etc/environment ) ; do export $line ; done, if the file format is key=value. –  Daniel Beck Sep 25 '11 at 11:38
    
Works for me without an export... –  Izkata Mar 30 at 14:44
add comment

1 Answer

up vote 42 down vote accepted

One thing you are mistaken about is that /etc/environment requires a reboot to reload. This is incorrect. The only time the file is read is on login, when the PAM stack is activated – specifically pam_env.so, which reads the file.

Logging out and back in would apply the changes – and in fact you must do this if you want all your processes to receive the new environment. All other "solutions"2 will only apply the environment to the single shell process, but not to anything you launch through the GUI including new terminal windows.1

If you're fine with that, though – the lack of export commands can be compensated for with set -a and set +a. However, it still remains a poor way, as the file doesn't use quoting either. But this should work fine:

while read -r env; do export "$env"; done

1 GNOME Session Manager provides a way to change its own environment, but only during the Initialization phase:

$ gdbus call -e -d org.gnome.SessionManager -o /org/gnome/SessionManager \
    -m org.gnome.SessionManager.Setenv "foo" "bar"
Error: GDBus.Error:org.gnome.SessionManager.NotInInitialization: Setenv
    interface is only available during the Initialization phase

2 gdb is not a solution, but can be used sometimes. You have to attach it to the running processes of your session manager (e.g. gnome-session), your window manager (e.g. gnome-shell or openbox), your taskbar/panel if any (e.g. xfce4-panel), and generally anything else that possibly would run stuff. For each of those processes, you need to attach gdb to it by PID, invoke the putenv() function using p, then detach using q:

$ sudo gdb -p $(pidof gnome-session)
GNU gdb (GDB) 7.7.1
[verbage...]
Attaching to process 718
[more verbage...]
0x00007fc2cefed81d in poll () from /usr/lib/libc.so.6
(gdb) p putenv("FOO=bar")
$1 = 0
(gdb) p putenv("BAZ=qux")
$2 = 0
(gdb) q
A debugging session is active.
Quit anyway? (y or n) y
Detaching from program: /usr/bin/gnome-session, process 718

Note that the debugger pauses the process, therefore you must attach to compositing window managers only from another tty (virtual console) or over SSH, otherwise the screen would freeze.

In addition to that, you should also update the environment used by dbus-daemon:

$ gdbus call -e -d org.freedesktop.DBus \
                -o /org/freedesktop/DBus \
                -m org.freedesktop.DBus.UpdateActivationEnvironment \
                "{'FOO': 'bar', 'BAZ': 'qux'}"
()
share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.