From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Reviving Gnus after suspend/hibernation Date: Sat, 29 Oct 2011 12:13:04 -0400 Message-ID: References: <87wrc2qmog.fsf@gnu.org> <877h3ule0y.fsf@lifelogs.com> <87hb2ucox4.fsf@lifelogs.com> <83lis6b8t9.fsf@gnu.org> <8762jajn5q.fsf@lifelogs.com> <87ehxym87k.fsf@lifelogs.com> <87mxckx3hx.fsf@lifelogs.com> <87mxcksc87.fsf@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1319904797 22942 80.91.229.12 (29 Oct 2011 16:13:17 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sat, 29 Oct 2011 16:13:17 +0000 (UTC) Cc: emacs-devel@gnu.org To: Jason Rumney Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Oct 29 18:13:12 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1RKBWx-00007c-JG for ged-emacs-devel@m.gmane.org; Sat, 29 Oct 2011 18:13:11 +0200 Original-Received: from localhost ([::1]:45569 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RKBWx-0007Cf-36 for ged-emacs-devel@m.gmane.org; Sat, 29 Oct 2011 12:13:11 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:44455) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RKBWt-00075Q-LK for emacs-devel@gnu.org; Sat, 29 Oct 2011 12:13:08 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RKBWs-0007ea-FM for emacs-devel@gnu.org; Sat, 29 Oct 2011 12:13:07 -0400 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.181]:6426 helo=ironport2-out.pppoe.ca) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RKBWs-0007eS-Ca; Sat, 29 Oct 2011 12:13:06 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av0EABwlrE5MCrTo/2dsb2JhbABCqWeBBoFyAQEEAVYjBQsLNBIUGA0kiBWzHYkCBKFEhEU X-IronPort-AV: E=Sophos;i="4.69,424,1315195200"; d="scan'208";a="145104891" Original-Received: from 76-10-180-232.dsl.teksavvy.com (HELO pastel.home) ([76.10.180.232]) by ironport2-out.pppoe.ca with ESMTP/TLS/ADH-AES256-SHA; 29 Oct 2011 12:13:05 -0400 Original-Received: by pastel.home (Postfix, from userid 20848) id E8F6C58E17; Sat, 29 Oct 2011 12:13:04 -0400 (EDT) In-Reply-To: <87mxcksc87.fsf@gnu.org> (Jason Rumney's message of "Sat, 29 Oct 2011 11:33:44 +0800") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.90 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 206.248.154.181 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:145766 Archived-At: >> The Linux kernel definitely does not (and barring a NAT router, or >> a resume with a different IP, or attempted communication on the link >> while you're sleeping, the TCP connection will be faithfully waiting >> for us when we resume). > The other end will close it after a timeout. Usually 5 minutes. I can assure you that I've seen TCP connections without any packet exchanged for a lot more than 5 minutes. And indeed most NAT routers wait longer than 5 minutes before considering a TCP connection as dead. The timeout you're talking about only exists if the connection uses the `tcp keepalive' feature (and yes, we want to use the tcp keepalive on those connections, and I added code for that). > But this isn't the problem I've experienced with Gnus after > suspend/resume. Gnus apparently knows the socket is closed, as it > very quickly reports the connection failure and starts working in > offline mode. What is missing is the ability to automatically reconnect > and continue, without going back to the Groups buffer and pressing M-g > (which inhibits the offline mode, as opposed to g, which doesn't). That's another issue ... ah yes: bug#9244 Stefan