From: Shenghuo ZHU <zsh@cs.rochester.edu>
Subject: Re: hang on entry to group
Date: 02 Oct 1999 18:05:10 -0400 [thread overview]
Message-ID: <5b670ph10p.fsf@giga.cs.rochester.edu> (raw)
In-Reply-To: Laura Conrad's message of "02 Oct 1999 15:17:36 -0400"
[-- Attachment #1: Type: text/plain, Size: 1385 bytes --]
>>>>> "LC" == Laura Conrad <lconrad@world.std.com> writes:
LC> pgnus 0.97 is hanging on entry to comp.os.linux.announce at the
LC> moment. The 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" "117-117")
LC> nntp-send-xover-command(117 117)
LC> nntp-retrieve-headers-with-xover((117 122 356 357 358 359 360 361 362) nil)
[...]
I guess I've located the bug. The ChangeLog and patch follow and have
been committed to CVS.
LC> [lconrad@serpent tmp]$ 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 comp.os.linux.announce
LC> 211 278 85 362 comp.os.linux.announce group selected
LC> xover 117-117
LC> 420 No articles in specified range.
The response code 420 is a bit weird. In nntp-send-xover-command, Gnus
try to find out the XOVER command when nntp-server-xover is try. The
response code 420 cause Gnus disable XOVER, while here XOVER is right
command.
[...]
--
Shenghuo ZHU
1999-10-02 Shenghuo ZHU <zsh@cs.rochester.edu>
* nntp.el (nntp-send-xover-command): Wait for nothing if not
wait-for-reply.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 97-zsh3.diff --]
[-- Type: text/x-patch, Size: 692 bytes --]
Index: nntp.el
===================================================================
RCS file: /usr/local/cvsroot/gnus/lisp/nntp.el,v
retrieving revision 5.20
diff -u -r5.20 nntp.el
--- nntp.el 1999/09/27 15:19:05 5.20
+++ nntp.el 1999/10/02 21:55:07
@@ -1189,7 +1189,7 @@
(nntp-send-command-nodelete
"\r?\n\\.\r?\n" nntp-server-xover range)
;; We do not wait for the reply.
- (nntp-send-command-nodelete "\r?\n\\.\r?\n" nntp-server-xover range))
+ (nntp-send-command-nodelete nil nntp-server-xover range))
(let ((commands nntp-xover-commands))
;; `nntp-xover-commands' is a list of possible XOVER commands.
;; We try them all until we get at positive response.
next prev parent reply other threads:[~1999-10-02 22:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-02 19:17 Laura Conrad
1999-10-02 19:22 ` Laura Conrad
1999-10-02 22:05 ` Shenghuo ZHU [this message]
1999-10-03 4:15 ` Shenghuo ZHU
1999-10-03 6:27 ` Shenghuo ZHU
1999-10-03 7:07 ` Shenghuo ZHU
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=5b670ph10p.fsf@giga.cs.rochester.edu \
--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).