From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.user/2051 Path: news.gmane.org!not-for-mail From: "Chris B." Newsgroups: gmane.emacs.gnus.user Subject: Re: Stale connection? Date: Fri, 07 Feb 2003 12:13:53 +1000 Message-ID: References: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1138668622 13742 80.91.229.2 (31 Jan 2006 00:50:22 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 31 Jan 2006 00:50:22 +0000 (UTC) Original-X-From: nobody Tue Jan 17 17:30:06 2006 Original-Path: quimby.gnus.org!newsfeed.gazeta.pl!newsfeed.tpinternet.pl!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!news1.optus.net.au!optus!spool01.syd.optusnet.com.au!spool.optusnet.com.au!not-for-mail Original-Sender: unixbigot@pobox.com Original-Newsgroups: gnu.emacs.gnus User-Agent: Gnus/5.090014 (Oort Gnus v0.14) Emacs/21.2 (i386-pc-linux-gnu) Cancel-Lock: sha1:37TPneamHXsPiqcB2ERfWRFKmdk= Original-NNTP-Posting-Host: 210.49.46.62 Original-X-Trace: 1044583862 16717 210.49.46.62 Original-Xref: bridgekeeper.physik.uni-ulm.de gnus-emacs-gnus:2191 Original-Lines: 35 X-Gnus-Article-Number: 2191 Tue Jan 17 17:30:06 2006 Xref: news.gmane.org gmane.emacs.gnus.user:2051 Archived-At: chris@grierwhite.com (Christopher J. White) moved upon the face of the 'Net and spake thusly: > If I leave gnus up and running for a while, then check news > (g from group buffer: gnus-group-get-new-news), it frequently > hangs as if waiting for a timeout. I've found, however, that > if I go unplugged (J j), then plugged again (J j), then > check news, it is nice and fast. Is this normal behaviour? > If I leave gnus plugged for a significant time, is gnus > keeping the connection open on my end but the server > is terminating it, thus the long timeout? Any way to have > gnus automatically close the connection after a timeout > and then re-establish it as necessary? I get that happen to me, because I connect to the NNTP server through a NAT firewall. The firewall box flushes its NAT tables after, I think, 10 minutes of inactivity, which can easily be the time it takes to compose a detailed followup. I habitually do "C-x 5 b *Group* ^ C-n C O C-x 5 0" (pull up *Server* window, close and re-open NNTP connection) to recover from this state. It would be real nice if there were an easier way to detect/recover from stale NNTP connections. (Yeah, the proper solution is to eradicate NAT, which is evil and loathesome). --cjb