public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: "Leslie Newell" <Les@lnewell.free-online.co.uk>
To: "insight" <insight@sourceware.cygnus.com>
Subject: Re: Create binary distribution.
Date: Tue, 12 Dec 2000 08:53:00 -0000	[thread overview]
Message-ID: <00ec01c0645b$e87a3ae0$0200a8c0@leslie> (raw)
In-Reply-To: <3A35264E.58F2523B@firetalk.com>

I have already set the timeout to 1. The problem is that if the target is not responding and I try to download a file, Insight will
keep retrying 10 times for each packet. Even with a 6K file this is a lot of retries.... I wonder if this could be considered a bug
because if a packet fails there is no point sending the rest of the file.

Les


> Leslie Newell wrote:
> >
> > Also is there any way of setting remote timeout to less than one second or
> > the number of retries to less than 10? If a download fails Insight can sit
> > there for ages continually retrying each packet - I have had to resort to
> > the three finger salute (Ctrl Alt Del) a couple of times.
>
> You can use the "remotetimeout" variable to change the delay time. When
> I work on Cygwin, I always set it to 1: "set remotetimeout 1". There is
> no interface for this, so you'll need to type this into the console
> window (or put it in the init file: gdb.ini on windows, I think).
>
> Keith
>



  reply	other threads:[~2000-12-12  8:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <B5B9971A.3F20%jingham@apple.com>
     [not found] ` <39944D77.1BC31C2A@cygnus.com>
2000-08-14 13:57   ` RFC: bind of Enter keys to all buttons Syd Polk
     [not found]     ` <399865E4.E1562FB8@cygnus.com>
2000-08-15 13:20       ` Tom Tromey
     [not found]         ` <399ACB73.7EC597D9@cygnus.com>
2000-12-11 10:50           ` Create binary distribution Leslie Newell
2000-12-11 11:09             ` Keith Seitz
2000-12-12  8:53               ` Leslie Newell [this message]
2000-12-12  9:01                 ` Keith Seitz

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='00ec01c0645b$e87a3ae0$0200a8c0@leslie' \
    --to=les@lnewell.free-online.co.uk \
    --cc=insight@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).