From: Mark Borges <mdb@cdc.noaa.gov>
Subject: [Gnus-5.5] Changing news server -- how well does it work?
Date: 23 Apr 1998 12:23:01 -0600 [thread overview]
Message-ID: <vkwwcgtn22.fsf@cdc.noaa.gov> (raw)
My current newsfeed (news.colorado.edu) has become extremely flaky,
and I would like to move to an alternate as my primary server. I've
read through the `Changing Servers' node on the info pages, and am
very tempted to switch servers using gnus-change-server().
Does this work reasonably well, or will I find some unexpected and/or
undocumented surprises? In particular, I'm curious how the transition
will handle:
(1) cached news articles. I have saved many old articles to local
disk, and wonder if I'll continue to have access to them (with
their old article numbers) via the Gnus interface.
(2) nonexistent newsgroups. The current server subscribes to nearly
everything under the sun, including the clari.* hierarchy. The
alternate, is much more restrictive in what it offers (but it's
much faster for the more common newsgroups I'm interested in
following).
Any advice or tips would be greatly appreciated.
My current setup as reported by gnus-bug() is,
Gnus v5.5; nntp 5.0; nnml 1.0; nnmh 1.0; nndir 1.0
XEmacs 20.4 "Emerald" [Lucid] (sparc-sun-solaris2.5) of Tue Mar 24 1998 on gill
200 boulder InterNetNews NNRP server INN 1.4unoff2 7-Aug-95 ready (posting ok).
------------------ Environment follows ------------------
[ remainder elided, supplied on request ]
and the new (alternate) news server is running
200 news.boulder.noaa.gov InterNetNews NNRP server INN 1.7.2 08-Dec-1997 ready (posting ok).
--
-mb-
next reply other threads:[~1998-04-23 18:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-04-23 18:23 Mark Borges [this message]
1998-04-23 19:24 ` Dan Christensen
1998-04-27 21:09 ` Mark Borges
1998-04-28 1:48 ` 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=vkwwcgtn22.fsf@cdc.noaa.gov \
--to=mdb@cdc.noaa.gov \
/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).