[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <CF6D1CC2-4B42-4FF9-821F-C54C4553D710@mac.com>
Date: Sun, 6 May 2007 23:33:11 -0400
From: Kyle Moffett <mrmacman_g4@....com>
To: David Lang <david.lang@...italinsight.com>
Cc: Pavel Machek <pavel@....cz>,
Nigel Cunningham <nigel@...el.suspend2.net>,
"Rafael J. Wysocki" <rjw@...k.pl>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Pekka J Enberg <penberg@...helsinki.fi>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: Back to the future.
On May 06, 2007, at 22:13:51, David Lang wrote:
> anyone who is doing a hibernate or suspend who expect all the
> network connections to be working afterwords is dreaming or
> smokeing something.
>
> this is just another way that the failure can show up.
>
> in fact, I would say that it would probalby be a nice thing to do
> for intervening firewalls and external servers if a suspend closed
> all external TCP connections rather then leaving them dangling
> (eating up resources until they time out)
>
> if you software can't tolorate the network connection going away on
> you it will have problems in normal operation anyway, let alone
> when you suspend/hibernate your machine.
Yeah, for suspend-to-ram+resume and for snapshot+restore you probably
want userspace to support some kind of initscript-like mechanism
which is triggered by the lid-switch or something before calling into
the kernel. That way it can close network connections mostly-nicely
and down network interfaces before suspending, then re-run DHCP/
802.11/whatever configuration after resume/restore. That might not
be a bad place to handle NFS mounts and such too.
Cheers,
Kyle Moffett
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists