From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ted Zlatanov Newsgroups: gmane.emacs.devel Subject: Re: Reviving Gnus after suspend/hibernation Date: Fri, 28 Oct 2011 16:31:06 -0400 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: <87mxckx3hx.fsf@lifelogs.com> 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> Reply-To: emacs-devel@gnu.org NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1319833893 21187 80.91.229.12 (28 Oct 2011 20:31:33 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Fri, 28 Oct 2011 20:31:33 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Oct 28 22:31:26 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 1RJt5K-0002KD-6L for ged-emacs-devel@m.gmane.org; Fri, 28 Oct 2011 22:31:26 +0200 Original-Received: from localhost ([::1]:43332 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RJt5J-0004MS-PJ for ged-emacs-devel@m.gmane.org; Fri, 28 Oct 2011 16:31:25 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:51141) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RJt5H-0004MB-IE for emacs-devel@gnu.org; Fri, 28 Oct 2011 16:31:24 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RJt5G-0004Mf-DO for emacs-devel@gnu.org; Fri, 28 Oct 2011 16:31:23 -0400 Original-Received: from lo.gmane.org ([80.91.229.12]:38917) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RJt5F-0004Mb-Pz for emacs-devel@gnu.org; Fri, 28 Oct 2011 16:31:22 -0400 Original-Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1RJt5D-0002Ia-8W for emacs-devel@gnu.org; Fri, 28 Oct 2011 22:31:19 +0200 Original-Received: from c-76-28-40-19.hsd1.vt.comcast.net ([76.28.40.19]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 28 Oct 2011 22:31:19 +0200 Original-Received: from tzz by c-76-28-40-19.hsd1.vt.comcast.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 28 Oct 2011 22:31:19 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: emacs-devel@gnu.org Original-Lines: 23 Original-X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: c-76-28-40-19.hsd1.vt.comcast.net X-Face: bd.DQ~'29fIs`T_%O%C\g%6jW)yi[zuz6; d4V0`@y-~$#3P_Ng{@m+e4o<4P'#(_GJQ%TT= D}[Ep*b!\e,fBZ'j_+#"Ps?s2!4H2-Y"sx" Mail-Copies-To: never User-Agent: Gnus/5.110018 (No Gnus v0.18) Emacs/24.0.90 (gnu/linux) Cancel-Lock: sha1:UfNyTYNSjjQAZt6Mq/+PHmRBP68= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-Received-From: 80.91.229.12 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:145729 Archived-At: On Thu, 27 Oct 2011 20:33:23 -0400 Stefan Monnier wrote: >> You're right, but on suspend&resume we should not have to wait for the >> TCP connection to time out. Let's assume it's closed in that specific >> case and set the keepalive for general use. SM> It strikes me as a non-Emacs-specific problem, so maybe the OS should SM> kill its TCP connection between suspend and resume. It probably does. >> Is this just a GnuTLS problem? Does any of the rest of Emacs have >> issues with hung connections? SM> I've been suffering from it for many years. I'm not sure if it SM> affects NNTP connections (it probably does) but it for sure affects SM> nnimap with gnutls-cli. That's a completely different use case, you're wrapping a process with arbitrary output when you use gnutls-cli. I'd prefer to work just on hung TCP connections. Ted