From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/5226 Path: main.gmane.org!not-for-mail From: hardaker@ece.ucdavis.edu (Wes Hardaker) Newsgroups: gmane.emacs.gnus.general Subject: Re: Connecting to a newsserver with nntp. Date: 22 Feb 1996 15:28:34 -0800 Organization: ha ahah haha ahahaha ahahaha ah Message-ID: References: <9602211956.AA09060@tito.cygnus.com> Reply-To: hardaker@ece.ucdavis.edu NNTP-Posting-Host: coloc-standby.netfonds.no X-Trace: main.gmane.org 1035145862 32213 80.91.224.250 (20 Oct 2002 20:31:02 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 20 Oct 2002 20:31:02 +0000 (UTC) Cc: ding@ifi.uio.no Return-Path: ding-request@ifi.uio.no Original-Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by deanna.miranova.com (8.7.3/8.6.9) with SMTP id QAA32146 for ; Thu, 22 Feb 1996 16:20:58 -0800 Original-Received: from chroma.ece.ucdavis.edu (hardaker@chroma.cipic.ucdavis.edu [128.120.67.31]) by ifi.uio.no with ESMTP (8.6.11/ifi2.4) id ; Fri, 23 Feb 1996 00:28:49 +0100 Original-Received: by chroma.ece.ucdavis.edu (1.37.109.16/Ultrix3.0-C/eecs 1.1) id AA116831721; Thu, 22 Feb 1996 15:28:41 -0800 Original-To: larsi@ifi.uio.no (Lars Magne Ingebrigtsen) X-Face: #qW^}a%m*T^{A:Cp}$R\"38+d}41-Z}uU8,r%F#c#s:~Nzp0G9](s?,K49KJ]s"*7gvRgA SrAvQc4@/}L7Qc=w{)]ACO\R{LF@S{pXfojjjGg6c;q6{~C}CxC^^&~(F]`1W)%9j/iS/IM",B1 M.?{w8ckLTYD'`|kTr\i\cgY)P4 X-Url: http://www.ece.ucdavis.edu/~hardaker In-Reply-To: larsi@ifi.uio.no's message of 22 Feb 1996 07:01:41 +0100 Original-Lines: 47 Xref: main.gmane.org gmane.emacs.gnus.general:5226 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:5226 >>>>> "Lars" == Lars Magne Ingebrigtsen 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