[Slackbuilds-users] Suggestion for Sourceforge mirrors

[alkos333]

I've always used -T (--connect-timeout) =5 and haven't had any problems with
that so far.

On 9/19/07, Eric Hameleers (SBo) <alien at slackbuilds.org> wrote:
>
> Niki Kovacs schreef:
> > Hi,
> >
> > More often than not, packages can't be downloaded from the various
> > Sourceforge mirrors.
> >
> > One exception I noticed: the Switch mirror
> > (http://switch.dl.sourceforge.net) is *always* reachable, at least in my
> > experience over the last few years. Is it that the swiss are so good at
> > serving files than they are at making wristwatches? Who knows?
> >
> > Suggestion: use a direct link to the switch mirror for SF-hosted source
> > tarballs.
>
> I think I would never allow the use of a single SourceForge mirror in
> a SBo submission.
> I used to use a single mirror site long ago, until that mirror went
> offline and I had to update all my scripts.
> It is better (and works all the time) to add "--connect-timeout=30" to
> the wget command of a sf.net download. When the first mirror does not
> answer, wget switches to the next after those 30 seconds, and so on,
> until it finds one that answers. May take a little longer but you will
> get your  download.
>
> Eric
> _______________________________________________
> Slackbuilds-users mailing list
> Slackbuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20070920/f3c02038/attachment-0002.html