From: Shenghuo ZHU <zsh@cs.rochester.edu>
Subject: Re: gnus hangs on entry to group
Date: 29 Oct 1999 11:50:21 -0400 [thread overview]
Message-ID: <2nzox2tbcy.fsf@tiger.jia.vnet> (raw)
In-Reply-To: Laura Conrad's message of "29 Oct 1999 07:58:34 -0400"
>>>>> "LC" == Laura Conrad <lconrad@world.std.com> writes:
LC> I have reported a problem similar to this, but I don't remember this
LC> particular backtrace, so I mention it again.
LC> I'm getting news from leafnode on localhost. This morning, pgnus 0.97 hangs
LC> when I try to enter the group rec.music.early.
LC> The debug-on-quit backtrace is:
LC> Signaling: (quit)
LC> accept-process-output(#<network connection "nntpd" ("nntp" . "localhost") state:run> 1)
LC> nntp-accept-process-output(#<network connection "nntpd" ("nntp" . "localhost") state:run>)
LC> nntp-send-command-nodelete("\r?\n\\.\r?\n" "XOVER" "123-123")
LC> nntp-send-xover-command(123 123)
LC> nntp-retrieve-headers-with-xover((123 152 231 268 270 1043 1303 1359 1360 1361) nil)
LC> nntp-retrieve-headers((123 152 231 268 270 1043 1303 1359 1360 1361) "rec.music.early" "localhost" nil)
LC> gnus-retrieve-headers((123 152 231 268 270 1043 1303 1359 1360 1361) "rec.music.early" nil)
LC> gnus-cache-retrieve-headers((123 152 231 268 270 1043 1303 1359 1360 1361) "rec.music.early" nil)
LC> gnus-retrieve-headers((123 152 231 268 270 1043 1303 1359 1360 1361) "rec.music.early" nil)
LC> gnus-select-newsgroup("rec.music.early" nil nil)
LC> gnus-summary-read-group-1("rec.music.early" nil nil nil nil nil)
LC> gnus-summary-read-group("rec.music.early" nil nil nil nil nil nil)
LC> gnus-group-read-group(nil)
LC> call-interactively(gnus-group-read-group)
LC> And telneting gives:
LC> [lconrad@serpent november]$ telnet localhost 119
LC> Trying 127.0.0.1...
LC> Connected to localhost.
LC> Escape character is '^]'.
LC> 200 Leafnode NNTP Daemon, version 1.9.4 running at serpent.local
LC> group rec.music.early
LC> 211 1244 118 1361 rec.music.early group selected
LC> xover 123-123
LC> 420 No articles in specified range.
420 is really bad. In some NNTPD, it is supposed to return "\n.\n"
followed by a "2xx" when there is no articles in specified
range. Although I can not find bug in `nntp-send-command-nodelete'
(actually in `nntp-wait-for'), I fixed a bug in
`nntp-send-xover-command'. I've committed it to CVS a few weeks ago.
In your backtrace, `nntp-send-xover-command' only got two arguments
(third argument `wait-for-reply' is nil), so we don't suppose it will
wait for something (unless it is a first (`try') action). The bug
cause gnus wait. Though, gnus wouldn't be hanging if `nntp-wait-for'
worked properly, I guess.
In addition, I also suggest you set `nntp-server-xover' to "XOVER",
the "420" response may mislead gnus to disable XOVER.
[...]
--
Shenghuo ZHU
prev parent reply other threads:[~1999-10-29 15:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-29 11:58 Laura Conrad
1999-10-29 15:50 ` Shenghuo ZHU [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=2nzox2tbcy.fsf@tiger.jia.vnet \
--to=zsh@cs.rochester.edu \
/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).