Re: Connecting to a newsserver with nntp.

[hardaker@ece.ucdavis.edu (Wes Hardaker)]

>>>>> "Lars" == Lars Magne Ingebrigtsen <larsi@ifi.uio.no> writes:

    gsstark@MIT.EDU (Greg Stark) writes:

    >> The real answer regarding C-g is to implement asynchronous
    >> backend interfaces.  Then Gnus can initiate connections to the
    >> nntp backend and your mail backend and allow you to read your
    >> mail while the nntp backend is still waiting to time out.  Lars
    >> has already indicated that this is in the cards for Red Gnus.
    >> (Right Lars?)

    Lars> Yup.  I've written parts of if already, even.

You know, one of the more annoying things I've been meaning to talk
about just came into my mind.

Here was my setup:

local nntp server
A distant nntp server as a second server.  

- sgnus was configured to check for new news-groups on both servers.
- I had subscribed to something like 3-5 newsgroups on the second server.

The second server is currently in-operational, but only halfway so.
It will let me connect to it, but immediately dis-connects me (note:
much different than connect-refused).  This caused sgnus to report
'lost connection with nntp server' upon entry every time.

So...  I gave up on the server and unsubscribed to the subscribed
newsgroups, and removed the server from the check-for-new-groups
server's list (whatever the @#%$ variable is).

Didn't work.  Still got the connection refused messages (which was a
pain since a lot of my local groups ended up with '*'s next to them
instead of article numbers (explain that one!) and because it never
properly drew the group buffer (the graphic GNUS local was always
still there till I hit the 'l' key).

I ended up going into the .newsrc.eld file and removing all instances
of the remote server/group entries in it by hand.  What I was suprised
to see was that there were like two entries per group.  Wierd again.

Why am I typing all this for you to read?
Beats the hell out of me...

Wes