On Sat, Sep 18, 2010 at 10:12 AM, Daniel Rogers <dsrogers@xxxxxx> wrote: > I've done exactly this, though it required quite a bit more magic. You > can't run from just any user session. It has to be a user session that > knows whatever environment is necessary to connect to an existing gconf > daemon. Otherwise the effects will not be persistent. > > The only way I was able to get it to work was to add: > > xml:readonly:$(HOME)/.nm/gconf > > To my users $HOME/.gconf.path.mandatory > > Then create a proxy configuration file as a gconftool dump: > > gconftool --dump /system/proxy > ~/.nm/system.proxy.xml > gconftool --dump /system/http_proxy > ~/.nm/system.http_proxy.xml > > Then when the network comes up set the properties in $HOME/.nm/gconf > without a running gconfd with gconftool --direct: > > gconftool --direct --config-source=xml:readwrite:$HOME/.nm/gconf --load= > $HOME/.nm/system.proxy.xml /system/proxy > gconftool --direct --config-source=xml:readwrite:$HOME/.nm/gconf --load= > $HOME/.nm/system.http_proxy.xml /system/http_proxy What does "--load" do? It isn't described in the man page for gconftool. When do specify the proxy values? Is that a one time thing? -- Darren Hart _______________________________________________ gnome-list mailing list gnome-list@xxxxxxxxx http://mail.gnome.org/mailman/listinfo/gnome-list
