On Sun, May 03, 2015 at 05:09:20PM +0530, Avinash Sonawane wrote: > may be it's file permissions. For me > $ ls -la /etc/environment /etc/sudoers > -rw-r--r-- 1 root root 117 May 2 17:41 /etc/environment > -r--r----- 1 root root 778 May 3 16:13 /etc/sudoers
There's nothing wrong with the file permissions. By default, root's shell reads /etc/environment, but users do not. To be honest I'm not sure why that is the case. You can configure your user(s) to source /etc/environment by adding '. /etc/environment' to their ~/.bashrc files (assuming they still use bash). To solve your specific apt-related problem, you can also add 'Defaults env_file += /etc/environment' to sudoers and it will be sourced by sudo when you use it to invoke another command. (IMHO that's preferable to whitelisting the http_proxy env variable). However it wouldn't be in your user's environment and you might want it for wget, curl, etc. as a non-root user, too. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/[email protected]
