From: Michael Lamoureux <lamour@engin.umich.edu>
Cc: ding@ifi.uio.no
Subject: Re: connect timeouts?
Date: 24 Jul 1996 12:31:05 -0400 [thread overview]
Message-ID: <6ivu3ux8vg6.fsf@erpland.engin.umich.edu> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of 24 Jul 1996 06:46:00 +0200
"lars" == Lars Magne Ingebrigtsen <larsi@ifi.uio.no> writes:
lars> Michael Lamoureux <lamour@engin.umich.edu> writes:
>> I figure if I'm stupid enough to keep trying to connecting to a
>> server that I'm not allowed to access, you should let me beat my
>> head against the wall until it bleeds...
lars> Well, yes. But no. :-) Say you read ten foreign groups from
lars> the "nntp:flaky" server, and you press `g'. Gnus will then try
lars> to activate these ten groups. If the first attempt at
lars> connecting fails, it's probably not very productive to try to
lars> reconnect to the server 9 more times?
No, but mine is not a foreign server... Does gnus not keep track of
which is the primary server and which are foreign?
lars> Perhaps there should be a time-out to the denials, but I don't
lars> think so.
perhaps. Or maybe it should just skip that server for the remainder
of *this* pass (i.e., until the 'g' operation has completed). That
way I get the benefit that you mention as well as the operation that I
want.
lars> Just use `^' to see the server status and remove the denials at
lars> will.
I'll take a look at this...
thanks,
Michael
next prev parent reply other threads:[~1996-07-24 16:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-07-23 0:04 robert
1996-07-23 7:01 ` Lars Magne Ingebrigtsen
1996-07-24 4:07 ` Michael Lamoureux
1996-07-24 4:46 ` Lars Magne Ingebrigtsen
1996-07-24 16:31 ` Michael Lamoureux [this message]
1996-07-25 3:50 ` Lars Magne Ingebrigtsen
1996-07-25 12:57 ` Michael Welsh Duggan
1996-07-27 17:18 ` 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=6ivu3ux8vg6.fsf@erpland.engin.umich.edu \
--to=lamour@engin.umich.edu \
--cc=ding@ifi.uio.no \
/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).