From: Ken Raeburn <raeburn@cygnus.com>
Subject: gnus loops if nntp server connection closes without sending output
Date: Sun, 1 Mar 1998 21:58:55 -0500 (EST) [thread overview]
Message-ID: <199803020258.VAA16137@kr-pc.cygnus.com> (raw)
I'm trying to contact an nntp server through a tcp forwarder (ssh).
The forwarder accepts the connection, but then if the news server
cannot be reached, it closes it.
The loop in nntp-wait-for does not appear to handle a closed
connection, where no amount of waiting will produce output from the
closed pipe. So nntp-open-connection loops endlessly. I tried making
nntp-wait-for simply raise an error in this case, but that aborts the
gnus invocation, and doesn't permit the reading of groups from other
servers.
I'm looking at qgnus-0.32, but the announcements for 0.33 and 0.34
don't indicate any change in this area.
Ken
next reply other threads:[~1998-03-02 2:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-03-02 2:58 Ken Raeburn [this message]
1998-03-07 12:51 ` Lars Magne Ingebrigtsen
1998-03-08 6:20 ` Ken Raeburn
1998-03-08 12:40 ` 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=199803020258.VAA16137@kr-pc.cygnus.com \
--to=raeburn@cygnus.com \
/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).