From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: joakim@verona.se Newsgroups: gmane.emacs.devel Subject: Re: Determining whether a TCP connection is up Date: Tue, 06 Aug 2013 11:59:12 +0200 Message-ID: References: <87txj64vbx.fsf@dex.adm.naquadah.org> <878v0g1l55.fsf@dex.adm.naquadah.org> <87zjsvxkur.fsf@dex.adm.naquadah.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1375783186 7366 80.91.229.3 (6 Aug 2013 09:59:46 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 6 Aug 2013 09:59:46 +0000 (UTC) Cc: emacs-devel@gnu.org To: Lars Magne Ingebrigtsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Aug 06 11:59:47 2013 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1V6e3P-0005nf-5O for ged-emacs-devel@m.gmane.org; Tue, 06 Aug 2013 11:59:47 +0200 Original-Received: from localhost ([::1]:55437 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V6e3O-0007jS-PL for ged-emacs-devel@m.gmane.org; Tue, 06 Aug 2013 05:59:46 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:39389) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V6e3F-0007j7-9p for emacs-devel@gnu.org; Tue, 06 Aug 2013 05:59:44 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1V6e38-0006q7-Cq for emacs-devel@gnu.org; Tue, 06 Aug 2013 05:59:37 -0400 Original-Received: from mx2.bahnhof.se ([213.80.101.12]:49459) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V6e38-0006pm-60 for emacs-devel@gnu.org; Tue, 06 Aug 2013 05:59:30 -0400 Original-Received: from localhost (mf.bahnhof.se [213.80.101.20]) by mx2-reinject (Postfix) with ESMTP id 8DF877AF286; Tue, 6 Aug 2013 11:59:27 +0200 (CEST) X-Virus-Scanned: by amavisd-new using ClamAV at bahnhof.se (MF2) Original-Received: from mf2.bahnhof.se ([127.0.0.1]) by localhost (mf2.bahnhof.se [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8YsfJlu+OpAJ; Tue, 6 Aug 2013 11:59:23 +0200 (CEST) Original-Received: from mta.verona.se (h-235-102.a149.priv.bahnhof.se [85.24.235.102]) by mf2.bahnhof.se (Postfix) with ESMTP id 6CD8C940105; Tue, 6 Aug 2013 11:59:23 +0200 (CEST) Original-Received: from localhost (unknown [127.0.0.1]) by mta.verona.se (Postfix) with ESMTP id 4A1B84E0F02; Tue, 6 Aug 2013 09:59:13 +0000 (UTC) X-Virus-Scanned: amavisd-new at verona.se Original-Received: from mta.verona.se ([127.0.0.1]) by localhost (exodia.verona.se [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x_D1l5AUfPqA; Tue, 6 Aug 2013 11:59:12 +0200 (CEST) Original-Received: from exodia.verona.se (www.verona.se [192.168.200.15]) by mta.verona.se (Postfix) with ESMTP id 55FC84E0211; Tue, 6 Aug 2013 11:59:12 +0200 (CEST) In-Reply-To: <87zjsvxkur.fsf@dex.adm.naquadah.org> (Julien Danjou's message of "Tue, 06 Aug 2013 10:51:56 +0200") User-Agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/24.3.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Mac OS X 10.x X-Received-From: 213.80.101.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:162446 Archived-At: Julien Danjou writes: > Did someone take a look at how other IMAP clients handles such > situation? > > Weirdly enough, Gnus is the only one to show such issues, whereas I > can't recall ever having this problem in mutt nor seeing it in Evolution > or Thunderbird. And I don't believe in magic. I used to have this problem a lot. nowadays I just remote my Emacs entirely, with x2go, so I dont have the problem anymore. When I did have it I noticed some things: - Running a local caching proxy dns helped a bit, but not entirely - I could trick emacs into understanding the connection was gone, by: - killing connection - noticing which sockets were hanging with netstat - making new trick interfaces with the same IP:s as the hanging remote This used to work, but was tedious. I notice the same sort of issues with NFS mounts also. There are various flags for NFS mounts that supposedly help, but not for me. The Linux kernel network stack doesnt seem designed with mobile networking in mind. So, to summarize, x2go was the best thing I did in a long time :) (not that x2go is flawless, either) -- Joakim Verona