Am Donnerstag, 11. Juli 2013, 13:37:06 schrieb Martin Weber:
It seems the curl command in obsworker ignores the no-proxy settings and tries to download the worker code from our proxy.
OTOH, if I log in as root and issue a 'rcobsworker start', it does _not_ fail. Of course, when you log in, the proxy environment variables are set, but if obsworker is run as a child of the init process, none of theses env vars are set.
In the obsworker code, I see that it sources /etc/sysconfig/proxy, but this sets shell variables, not env variables.
Okay, I added some export lines there. Also for next 2.4 release, would be nice if you can test if that works for you. thanks! adrian -- Adrian Schroeter email: adrian@suse.de SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org