From: Scott Hofmann <shofmann@intertv.com>
Subject: Some thoughts on NoCeM and switching servers
Date: Thu, 18 Sep 1997 10:29:58 -0400 [thread overview]
Message-ID: <199709181429.KAA11098@kyoto.intertv.com> (raw)
Recently, due to a job change, I switched NNTP servers. During the switch
I wound up fighting Gnus (both 5.4.66 and Quassia 0.5) at two separate
occasions, both of which should be easily remediable.
The first problem I had was in logging into the NNTP server. It's a secure
server that requires a login and password, so I initiallly set
nntp-authinfo-function to nntp-send-nosy-authinfo. When I ran gnus, it did
stuff in a backwards order: it connected to the NNTP server, and then asked for
the login information. This caused gnus to (apparently) hang while trying to
read the active file, because the NNTP server refused to talk to gnus. I was
able to solve this problem by adding nntp-send-nosy-authinfo to
nntp-server-opened-hook, which got gnus to do things in the correct order
(login, then fetch the active file). At the barest minimum, this should be
documented somewhere, preferably in the "Starting Up" section.
The second problem was with NoCeM. When there is no NoCeM/active file, it would
be nice if NoCeM behaved as if gnus-nocem-expiry-wait was set to 0 - on my new
NNTP server there were over 10,000 unread messages in news.lists.filters alone,
and given how slow my NNTP connection is it would have taken gnus nearly 12
hours to read news.lists.filters alone, much less alt.nocem.misc and the other
NoCeM groups. It seems like this could be fixed with a bit of elisp - if NoCeM
is creating its active file then it should consider all NoCeM messages as
"read" so that gnus doesn't spend hours and hours reading NoCeM messages during
gnus' first invocation on a new server.
scott
--
J. Scott Hofmann
shofmann@intertv.com
next reply other threads:[~1997-09-18 14:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-09-18 14:29 Scott Hofmann [this message]
1997-09-20 18:13 ` Lars Magne Ingebrigtsen
1997-09-21 3:24 ` Don Croyle
1997-09-21 16:19 ` Lars Magne Ingebrigtsen
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=199709181429.KAA11098@kyoto.intertv.com \
--to=shofmann@intertv.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).