Bug 132161 - Disabling the proxy doesn´t unset the environment variables
Summary: Disabling the proxy doesn´t unset the environment variables
Status: RESOLVED WONTFIX
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: RC 1
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Katarina Machalkova
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-03 16:32 UTC by Michael Stather
Modified: 2006-08-11 07:14 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Stather 2005-11-03 16:32:42 UTC 
When I´ve enabled a Proxy in YaST, the environment variables are set according to what I entered. But when I disable the proxy they remain set until I restart my maching. IMHO they should be unset immediately.
Comment 1 Katarina Machalkova 2006-08-10 13:17:21 UTC 
Well, YaST proxy module does not update appropriate environment variables on per-user basis, but rather on system-wide basis i.e. it sets appropriate values in /etc/sysconfig/proxy. Now the only way how to unset $*_proxy variable for particular user, is to log out and log in again.

The solution would be to adjust aaa_base scripts to set/unset environment variables for user according to sysconfig each time user opens a new shell so that logging out and back in would no longer be necessary (don't know if that's possible, though). Therefore, setting NEEDINFO to aaa_base maintainer. 

Rudi, if this is nothing for you, I'll close this as 'wontfix', since there's no way for YaST to adjust environment variables for each individual user in order to take the effect immediately. Btw, what happened to SuSEconfig "profiles" module ?
Comment 2 Ruediger Oertel 2006-08-10 16:39:01 UTC 
SuSEconfig.profiles was removed before SUSE-Linux-10.0 already.
changelog entry in aaa_base was:
Wed Aug  3 18:54:27 CEST 2005 - werner@suse.de

- Fix new mount point check in boot.crypto (bug #100536)
- Add profile.sh and profile.csh as replacement for
  the removed SuSEconfig.profile for runtime user profile.


updating the environment for already running processes is probably not doable
at all ...
Comment 3 Katarina Machalkova 2006-08-11 07:14:57 UTC 
OK, closing as 'wontfix' then.