Hi Dimitris, On 2013-03-29 at 04:25 PDT, Dimitris Zarras wrote: > Would putting > > http_proxy=http://127.0.0.1:4545/ > export http_proxy > > in /etc/bash.bashrc or > > http_proxy=http://127.0.0.1:4545/ > > in /etc/environment do the trick, or do I need to add it as a command > line argument to steamcmd.sh ?
Yes, setting the http_proxy environment variable seems to do the trick. It even suffices to just place the IP address and port into the variable, i.e. 127.0.0.1:4545. You have multiple options of setting this environment variable so that SteamCMD sees it. Quite possibly the safest way to do this is just to specify it right before the command, e.g. http_proxy="127.0.0.1:4545" ./steamcmd.sh +runscript update_all.steamcmd If, for some reason, your shell is totally stupid and doesn't allow for this, you can work around it using the "env" program, which launches a command under a modified environment (i.e. what your shell was supposed to do in the first place). env http_proxy="127.0.0.1:4545" ./steamcmd.sh +runscript update_all.steamcmd Hope that helps. Cheers, ~~ Ondra _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
