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.
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? 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? > > apt uses a timeout of 120 seconds (2 minutes), which seems reasonable to me. > Feedback is given to the user so that they know what apt is trying to do at > that point, so it does not look as if the process is unexpectedly hung. > > -- > - mdz __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free web site building tool. Try it! http://webhosting.yahoo.com/ps/sb/
