Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: Re: connect timeouts?
Date: 24 Jul 1996 06:46:00 +0200	[thread overview]
Message-ID: <w8sraq2p8c7.fsf@hler.ifi.uio.no> (raw)
In-Reply-To: Michael Lamoureux's message of 24 Jul 1996 00:07:33 -0400

Michael Lamoureux <lamour@engin.umich.edu> writes:

> Why?  Our news server gets flakey every once in a while, and if I try
> to connect at the wrong time, then gnus is basically useless for
> reading news until I restart (I can, of course, still read mail, but
> that's not the point).  This is silly, because as soon as the news
> server is rebooted, it's ok, but how am I supposed to know when that
> is if gnus keeps refusing to connect?  (there are actually a handful
> of ways, but none of them are as easy as hitting 'g' ;-)
> 
> 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...

Well, yes.  But no.  :-) Say you read ten foreign groups from the
"nntp:flaky" server, and you press `g'.  Gnus will then try to
activate these ten groups.  If the first attempt at connecting fails,
it's probably not very productive to try to reconnect to the server 9
more times?

Perhaps there should be a time-out to the denials, but I don't think
so.  Just use `^' to see the server status and remove the denials at
will. 

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@ifi.uio.no * Lars Ingebrigtsen


  reply	other threads:[~1996-07-24  4:46 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 [this message]
1996-07-24 16:31       ` Michael Lamoureux
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=w8sraq2p8c7.fsf@hler.ifi.uio.no \
    --to=larsi@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).