|
Bugzilla – Full Text Bug Listing |
| Summary: | Disabling the proxy doesn´t unset the environment variables | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Michael Stather <kontakt> |
| Component: | YaST2 | Assignee: | Katarina Machalkova <kmachalkova> |
| Status: | RESOLVED WONTFIX | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | RC 1 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Michael Stather
2005-11-03 16:32:42 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 ? 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 ... OK, closing as 'wontfix' then. |