From: "Chris B." <unixbigot@pobox.com>
Subject: Re: Stale connection?
Date: Fri, 07 Feb 2003 12:13:53 +1000 [thread overview]
Message-ID: <saznp896vx.fsf@unixbigot.pobox.com> (raw)
In-Reply-To: <m28ywty0ro.fsf@bluesteel.grierwhite.com>
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
prev parent reply other threads:[~2003-02-07 2:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m28ywty0ro.fsf@bluesteel.grierwhite.com>
2003-02-06 15:03 ` Kai Großjohann
[not found] ` <m2ptq5ja8z.fsf@bluesteel.grierwhite.com>
2003-02-07 18:27 ` Kai Großjohann
2003-02-07 2:13 ` Chris B. [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=saznp896vx.fsf@unixbigot.pobox.com \
--to=unixbigot@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).