load on mirrors | was: kdelibs4c2a missing

[Thilo Six]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

Derek Broughton schrieb am 11.04.2006 20:23:

<snip>

> It's not something I've tried, but from observation it would appear that you
> can't _make_ apt get A from X and B from Y if both exist in both mirrors

That is what i recognized also.

> _but_ if you have multiple mirrors in your sources (it doesn't matter
> whether they are mirrors or really different repositories - apt can't tell
> the difference) apt will open them up in separate threads (to a default
> limit of four threads, iirc).  Then it may get the first file from the
> first mirror and the second from the second mirror.

Here i have a 2Mbit DSL line. When i use my local mirror wget tells me i
get 235kByte which is physicaly quite the maximum.
Personally i do not need to open connections to several mirrors it would
not speed up anything for me.

> This is certainly the behaviour where files are not common to different
> repositories, but I think I've also seen fallbacks - where package A was
> unavailable from mirror X (because of connection problems) getting it from
> mirror Y.

And this is the case where the "backup-mirror" line in sources.list
comes in. If you do update and see "could not connect" "file not found"
or any other error, then just replace this mirror (switching the #).

> However, I think it's moot with regard to having the identical URL specified
> twice, because I'm pretty sure apt throws away duplicates.

Sorry but after all no argument could convince me here so i stick with
my opinion.

But i will investigate this issue some more to find some facts about it.
I am also "only" a user and no mirror admin at last.
When i find someting more concrete i will post it here.

bye Thilo
- --
i am on Ubuntu 2.6 KDE
- - some friend of mine

gpg key: Ox4A411E09

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFEPDwigkdHiUpBHgkRA6KaAJwINq0jH/s5BXGRkK4wl6fOx/XFdQCg2Ysd
bytCF5+LL1YCKJmOaWRUI1U=
=BNKP
-----END PGP SIGNATURE-----