Bug#224121: acknowledged by developer (Re: apt-setup hangs if debian-non-us is not available)

[Matt Zimmerman <mdz@debian.org>]

On Fri, Jan 30, 2004 at 05:15:46AM -0800, solo turn wrote:

> somehow i missed the feedback that it tries to connect and wait for 2 minutes. so i got nervous,
> 2mins is a very long time for a fast internet connection. if it does not connect within 5-10 secs
> it should retry and then forget.

It is much better to have a timeout which is too long than one which is too
short.  You might be on a fast internet connection, but someone else could
be using dial-on-demand.

> so it would be possible to set it more appropriate with:
> 
> acquire::http::timeout "20";
> acquire::http::retries "1";
> 
> maybe you consider including such a setting in the example configuration in /doc?

Yes, in fact it can be included without even making a new release, because it
is already there. :-)

  // HTTP method configuration
  http 
  {
    Proxy "http://127.0.0.1:3128";;
    Proxy::http.us.debian.org "DIRECT";  // Specific per-host setting
    Timeout "120";
    Pipeline-Depth "5";
    
    // Cache Control. Note these do not work with Squid 2.0.2
    No-Cache "false";
    Max-Age "86400";     // 1 Day age on index files
    No-Store "false";    // Prevent the cache from storing archives    
  };


> and what i'm also wondering: when apt is downloading from an apt-proxy, it
> just opens one thread, while a direct connect opens two threads. why it
> does not do this for apt-proxy?

Ask apt-proxy.  I think the way that one works is to point apt at a CGI, so
if they are all pointing at the same CGI, as far as apt knows, they are the
same host.

-- 
 - mdz