From: David S Goldberg <david.goldberg6@verizon.net>
Subject: Re: server disconnect leads to "article not found"
Date: Wed, 12 Jun 2002 13:30:25 -0400 [thread overview]
Message-ID: <u8zlm9k9zgu.fsf@blackbird-2k.MITRE.ORG> (raw)
In-Reply-To: <m3d6ux9w23.fsf@merlin.emma.line.org> (Matthias Andree's message of "Wed, 12 Jun 2002 02:31:48 +0200")
I've seen this with other nntp servers (verizon and newsguy). What
happens to me is a little different, I think, but may be related to
the same issue.
1: I start reading news
2: One of the kids or my wife needs attention
3: In the interim the connection to the nntp server times out
4: I come back and try to read the next article ; it is bogusly marked
deleted
5: I try to go to the next next article, gnus realizes the connection
is gone, reestablishes it and properly finds that article.
6: I unmark the previously bogusly marked article and successfully
read it. I should note that it is necessary to read a different
article before unmarking and reading it, presumably because there's
a bogus article buffer associated with it, but I haven't done
enough troubleshooting to be sure
My workaround is to recognize the likely hood of a server time out and
M-: (gnus-close-server "newsguy") RET M-: (gnus-open-server "newsguy") RET
Before trying to read anything when I get back to gnus. I've been
seeing this for a long time now, much longer than Oort 0.7, probably
even before Oort but I'm less certain of that. I've not been using
Gnus at home for nearly as long as at work and don't recall what was
current when I set up at home.
--
Dave Goldberg
david.goldberg6@verizon.net
next prev parent reply other threads:[~2002-06-12 17:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-11 23:21 Matthias Andree
2002-06-12 0:31 ` Matthias Andree
2002-06-12 17:30 ` David S Goldberg [this message]
2002-06-13 0:37 ` Matthias Andree
2002-06-13 11:13 ` Matthias Andree
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=u8zlm9k9zgu.fsf@blackbird-2k.MITRE.ORG \
--to=david.goldberg6@verizon.net \
/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).