Mailinglist Archive: opensuse-factory (422 mails)
| < Previous | Next > |
Re: [opensuse-factory] global proxy configuration
- From: Dave Plater <dave.plater@xxxxxxxxxxx>
- Date: Wed, 21 Jan 2009 15:00:30 +0200
- Message-id: <49771C6E.1000408@xxxxxxxxxxx>
Dominique Leuenberger wrote:
konsole but yast is unable to do this, correct? As I said previously I
successfully stopped a fresh instance of zypper from using the proxy by
clearing the variable from the command line as root.
Regards
Dave P
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx
I understand from this that I can clear the variable myself from a rootOk I just tested, I disabled proxy via yast and then shut squid down.On 1/21/2009 at 1:15 PM, Dave Plater <dave.plater@xxxxxxxxxxx> wrote:
..curl was then cleaned out but the variable $http_proxy still contained
the proxy address and zypper ref failed. I then export http_proxy= and
zypper ref worked correctly. From this I would conclude yast proxy
settings should clear the environment variable when proxy is disabled
and the problem of logout/login being required would be solved, would
you agree?
You can't clear an environment variable from a parent process (shell). This
is simply not possible.
Check this schema
bash (env0)
yast2 (env0.1)
yast2-doSomething (env0.1.1)
zypper (env0.2)
Whenever you spawn a child process, the environment from the parent is copied
and that's the only environment you can modify. So if yast-doSomething
would clear the http_proxy, that would be completely useless for a later
start of zypper, as it will copy env0 again and create 0.2... so no go at
all...
Dominique
konsole but yast is unable to do this, correct? As I said previously I
successfully stopped a fresh instance of zypper from using the proxy by
clearing the variable from the command line as root.
Regards
Dave P
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx
| < Previous | Next > |