On Fri, Feb 24, 2006 at 12:34:45PM -0500, Bill Sommerfeld wrote:
> On Tue, 2006-02-21 at 12:11 -0600, Nicolas Williams wrote:
> > 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.
> >
> > The best thing to do in the short-term, IMO, on a GUI console login is
> > to pop-up a little ballon saying something to the effect that "you've
> > lost your network, things will hang, click here for some options."
>
> I wonder if we could get some mileage out of declaring certain
> TCP/RPC/... operations as "expendable", and failfast those on a link
> failure, while keeping others you care about (e.g.,
> ssh/imap/ftp/telnet/vpn/nfs etc.,) alive.
As a NWAM profile option ("if this is all that's running, kill it all,
umount -f and switch automagically").
Or as a socket option? But maybe I don't care about ssh (because I use
screen; yay for screen) or imap (because my client can reconnect), while
you do. So more app options?
