[opensuse-factory] proxy-management of yast2 bug?
Normally I m using no proxy while installing new packages. Today it was necessary to to configure a proxy. Yast2 package-manager worked fine with the proxy-settings but after deactivating the proxy when moving into another network yast2 did not find the repos until a reboot of the system. Ralf Prengel --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Ralf,
Please, look your $http_proxy values at prompt. Maybe there´s a
problem cleaning this values.
You can try clean this variable using unset or just a blank $http_proxy.
On shell, try:
export $http-proxy=""
Then try to update using Yast.
Cheers.
On Mon, Jun 9, 2008 at 3:33 PM, Ralf Prengel
Normally I m using no proxy while installing new packages. Today it was necessary to to configure a proxy. Yast2 package-manager worked fine with the proxy-settings but after deactivating the proxy when moving into another network yast2 did not find the repos until a reboot of the system.
Ralf Prengel --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
-- /\ Gabriel Stein gabrielstein@gmail.com MSN: gabrielstein@hotmail.com Administrador de Redes - Network Administrator Linux User #223750 +55 51 9357 3886 Porto Alegre - RS - Brasil --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Ehlo,
Yast2 package-manager worked fine with the proxy-settings but after deactivating the proxy when moving into another network yast2 did not find the repos until a reboot of the system.
This works as designed - proxy settings are environment variables and as it is not trivial to update the environment of already running process e.g. your desktop session, you need either to relogin or reboot. Yast writes proxy settings into /etc/sysconfig/proxy file and it is the login script (profile.sh) executed upon new login, that reads them and exports them. For the settings to take effect immediately, set your $http_proxy variable to empty string and, if you use login/password to access proxy, don't forget to clear also /root/.curlrc file. B. -- \\\\\ Katarina Machalkova \\\\\\\__o YaST developer __\\\\\\\'/_ & hedgehog painter
Katarina Machalkova schrieb:
Ehlo,
Yast2 package-manager worked fine with the proxy-settings but after deactivating the proxy when moving into another network yast2 did not find the repos until a reboot of the system.
This works as designed - proxy settings are environment variables and as it is not trivial to update the environment of already running process e.g. your desktop session, you need either to relogin or reboot. Yast writes proxy settings into /etc/sysconfig/proxy file and it is the login script (profile.sh) executed upon new login, that reads them and exports them.
For the settings to take effect immediately, set your $http_proxy variable to empty string and, if you use login/password to access proxy, don't forget to clear also /root/.curlrc file.
B. ok but why does it work in one direction? No proxy changing to proxy is working immediately but proxy changing to no proxy needs a relogin?
Ralf Prengel --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
This works as designed - proxy settings are environment variables and as it is not trivial to update the environment of already running process e.g. your desktop session, you need either to relogin or reboot. Yast writes proxy settings into /etc/sysconfig/proxy file and it is the login script (profile.sh) executed upon new login, that reads them and exports them.
ok but why does it work in one direction? No proxy changing to proxy is working immediately but proxy changing to no proxy needs a relogin?
In neither case should it work immediately :) Relogin is really needed in general situation. YaST package management (which uses libzypp media backend, which in turn uses libcurl) is however somehow special in this aspect. It reads /etc/sysconfig/proxy and also /root/.curlrc directly, therefore no_proxy -> proxy change is visible to YaST immediately. The change in opposite direction (proxy -> no_proxy) should clear /root/.curlrc file and disable proxy in sysconfig, but $http_proxy variable might still be set and I'm not sure whether libcurl actually does not prefer the environment to the configuration files. Anyway, CCing Jano (libzypp media backend fellow), he knows better :) B. -- \\\\\ Katarina Machalkova \\\\\\\__o YaST developer __\\\\\\\'/_ & hedgehog painter
Katarina Machalkova wrote:
This works as designed - proxy settings are environment variables and as it is not trivial to update the environment of already running process e.g. your desktop session, you need either to relogin or reboot. Yast writes proxy settings into /etc/sysconfig/proxy file and it is the login script (profile.sh) executed upon new login, that reads them and exports them.
ok but why does it work in one direction? No proxy changing to proxy is working immediately but proxy changing to no proxy needs a relogin?
In neither case should it work immediately :) Relogin is really needed in general situation. YaST package management (which uses libzypp media backend, which in turn uses libcurl) is however somehow special in this aspect.
It reads /etc/sysconfig/proxy and also /root/.curlrc directly, therefore no_proxy -> proxy change is visible to YaST immediately. The change in opposite direction (proxy -> no_proxy) should clear /root/.curlrc file and disable proxy in sysconfig, but $http_proxy variable might still be set and I'm not sure whether libcurl actually does not prefer the environment to the configuration files.
Anyway, CCing Jano (libzypp media backend fellow), he knows better :)
B. I use a local squid to limit my own bandwidth use, to avoid clogging the network and I switch proxy on and off in one session often. I have just used yast to enable proxy, installed a package using proxy, turned it off again and installed another at full speed with no proxy. I don't switch networks though. Regards Dave P
To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (4)
-
Dave Plater -
Gabriel Stein -
Katarina Machalkova -
Ralf Prengel