From: Graham Murray <graham@barnowl.demon.co.uk>
Subject: Re: Pterodactyl Gnus v0.52 is released
Date: 20 Nov 1998 15:30:08 +0000 [thread overview]
Message-ID: <m2iugafklb.fsf@barnowl.demon.co.uk> (raw)
In-Reply-To: <vxkk90qwiep.fsf@beaver.jprc.com>
Karl Kleinpaste <karl@justresearch.com> writes:
> What's your server incantation? I have an INN 1.7.2-insync as my
> native method and a very non-standard thing at CMU as a secondary,
> both of which have been happy with p0.5x. Did you upgrade a long way
> in the p0.X series just now?
The native method goes to an INN 1.7 server on this box. The only
secondary method is nnml. The first pgnus I applied was 0.33 (at the
same time as I upgraded OS and switched from emacs 19.34 and qgnus)
and I have applied every subsequent upgrade the same day as it was
released. I have only been running the local news server for a week,
before that I was using Agent mode.
> My first guess would have been that your server has decided it doesn't
> like multiple connections from one host (hence async retrieval is
> failing, on inability to open 2nd connection), but there's no reason
> for that to have taken a toll on you just with the latest version.
There are *no* errors shown in my INN logs. Also it seems strange that
it only affects the 2nd unread (in order on the summary screen)
article when entering a group. It is also strange that order of
reading affects the result. It only started happening when I moved
from 0.51 to 0.52. As an experiment, I reverted to 0.51 and the
problem went away. Coming back to 0.52 the problem returned.
prev parent reply other threads:[~1998-11-20 15:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-20 4:31 Lars Magne Ingebrigtsen
1998-11-20 8:49 ` Graham Murray
1998-11-20 10:52 ` Graham Murray
1998-11-20 14:25 ` Karl Kleinpaste
1998-11-20 14:59 ` Felix Lee
1998-11-20 15:25 ` Lars Magne Ingebrigtsen
1998-11-20 15:30 ` Graham Murray [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=m2iugafklb.fsf@barnowl.demon.co.uk \
--to=graham@barnowl.demon.co.uk \
/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).