I've always used -T (--connect-timeout) =5 and haven't had any problems with that so far. <br><br><div><span class="gmail_quote">On 9/19/07, <b class="gmail_sendername">Eric Hameleers (SBo)</b> <<a href="mailto:alien@slackbuilds.org">
alien@slackbuilds.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Niki Kovacs schreef:<br>> Hi,<br>><br>> More often than not, packages can't be downloaded from the various
<br>> Sourceforge mirrors.<br>><br>> One exception I noticed: the Switch mirror<br>> (<a href="http://switch.dl.sourceforge.net">http://switch.dl.sourceforge.net</a>) is *always* reachable, at least in my<br>> experience over the last few years. Is it that the swiss are so good at
<br>> serving files than they are at making wristwatches? Who knows?<br>><br>> Suggestion: use a direct link to the switch mirror for SF-hosted source<br>> tarballs.<br><br>I think I would never allow the use of a single SourceForge mirror in
<br>a SBo submission.<br>I used to use a single mirror site long ago, until that mirror went<br>offline and I had to update all my scripts.<br>It is better (and works all the time) to add "--connect-timeout=30" to
<br>the wget command of a <a href="http://sf.net">sf.net</a> download. When the first mirror does not<br>answer, wget switches to the next after those 30 seconds, and so on,<br>until it finds one that answers. May take a little longer but you will
<br>get your download.<br><br>Eric<br>_______________________________________________<br>Slackbuilds-users mailing list<br><a href="mailto:Slackbuilds-users@slackbuilds.org">Slackbuilds-users@slackbuilds.org</a><br><a href="http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users">
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users</a><br></blockquote></div><br>