morphy76 wrote:
> hello
>
> i use my laptop both at home and at office
>
> when i am in the office i have a proxy
>
> so i’ve configured 2 users (home and office), the latter has proxy
> configured
>
> but
>
> yast doesn’t use per-user configuration but the system proxy
> configuration, which is shared between home and office users
>
> what do you suggest about proxy configuration to avoid logout/login
> procedure to enable/disable system proxy?
Rather than looking at this as two users, I think you need
to look at this as two network profiles… but that naturally
suggests something similar to what you said you don’t like.
If you’re suspending between Work/Home, to avoid logouts, then you need to provide a proxy because you cannot alter the environment of running programs.
So use proxy on localhost, and have 2 config files, 1 for at work, and second for at home. Then restarting the daemon, when the networks restarted should suffice.
On Wed, 2009-12-09 at 18:46 +0000, morphy76 wrote:
> i would prefer to have one single user… and SCPM seems to be a good
> idea… i need to get deeper in it… thank you…
>
> btw… is it compatible with network manager?
Not sure. I’m not a big fan of network manager.
Unless you are hopping from network to network all of the
time and have NO CLUE (at all) about what a network is,
I wouldn’t use Network Manager for anything.
I am in the same situation except with three different configurations (direct access to network, office and client office). Personally I just use the GNOME system proxy applet and created three different locations for each configuration. I then just use the applet to switch proxies as needed. Many applications seem to pick up the change automatically however sometimes I do need to close and re-open an application but it has not been a big deal for me so far.
BTW, I change proxies constantly even when I am in the office as I have two network cables, one for accessing the net directly and one for the internal network. Throw in VPN access to the office and my day is one of constantly bouncing between networks and proxy servers. I find the network manager and the proxy applet with the proxies pre-defined by location works reasonably for me and while I’ve thought about scripting it at some point so far it hasn’t annoyed me enough to bother.
Yast may have issues with proxy that requires authentication. However as it is restarted, and run as root user changes to proxy configuration may take effect without local user logging out.
The issues seems to be HTTP & FTP configuration,rather than the general network profiles. You can avoid login/logout issues for all users, by always running a proxy on the localhost, that gets reconfigured for home or office and restarted.
On the use of profiles, you seem confused about what features are for instance ‘netgroups’. It’s likely you’re setting things which do not have the effect you expect.
I am not sure how switching profiles is meant to solve this avoiding login/logout, as IIRC they based on different boot configurations, nevermind avoiding need to login & logout, between locations.
nice point of view! why yast tells me that i need to logout/login on proxy changes when what’s done is for a root process?
with this question in mind, i can say “who cares about that message!!!” my proxy is configured in the gnome administration and changes works without logout/login
my last doubt is about the update applet… which runs as user… but it seems to use the yast configuration instead of the gnome one…
remains the problem to setup proxies when network changes… and now… let’s talk about profiles…
Because Environmental variables are set, which are designed to be a default for all system users.
with this question in mind, i can say “who cares about that message!!!” my proxy is configured in the gnome administration and changes works without logout/login
Because you have to fiddle in the GUI. It does not have an effect on commands like wget(1) which may use defaults set by Evironmentals.
my last doubt is about the update applet… which runs as user… but it seems to use the yast configuration instead of the gnome one…
Updates have to be done as root. User GNOME config must be ignored.
It would seem to be addressing problem to that solved by Network Manager, I do not know how widely used and tested SCPM is.
It would still seem to have a problem of requiring change in your web browsing configuration, that my suggestion avoids. Though you’ld need a script to flip used in network hooks dependant on location, between direct connect & Office configuration, to realise the benefit.