On Tue, Feb 21, 2006 at 12:11:51PM -0600, Nicolas Williams wrote: > On Tue, Feb 21, 2006 at 08:42:00AM -0800, Bart Smaalders wrote: > > If we don't do automatic reconfigs of network state, is there > > a way to insure that network operations depending on a currently > > unavailable network "fail fast"? If my wireless link has dropped, > > waiting for YP/DNS/LDAP to timeout is going to be rather tiresome; > > I'd much rather it failed right away with a "no route to host" > > kind of message.
> This is hard to address in the path of the hang -- the functions that > are hanging are hanging because that's the only thing they're expected > to do in these situations, and changing this behaviour isn't likely to > be feasible. One thing that comes to mind is that we could track network/server latency in base network services like name services and NFS and act on it: e.g., change the color/icon of the network monitor applet. We could also make sure that the X server, the window manager and the network monitor applet don't do the kinds of things that could hang on network services (I'm pretty sure they don't already), so that it is always possible to bring up the network monitor / NWAM applet and switch network profiles forcefully.
