Date: prev next · Thread: first prev next last


Hi,

Rainer Bielefeld wrote on 2011-04-23 11.46:

I checked again incomplete mirrors 2011-04-26 09:30 UTC.
Most mirrors now seem to be complete, only
<http://sunsite.informatik.rwth-aachen.de/ftp/pub/mirror/tdf/libreoffice/testing/>

still is empty. This mirror has been mentioned because of problems
several times.

thanks, I gave the admin a ping!

Even if mirrorbrain will not root to not existing files, we might run
into problems if lots of users want to download an announced new version
what only can be found on few mirrors? Currently I do not see that as a
heavy problem, we have a lot of mirrors. But we should continue watching
time until most mirrors are up to date to decide when a new version
should be announced. May be mirrorbrain provides useful statistics?

IMHO, MirrorBrain has a mirmon statistics interface that we could use. I just need to find out how it works... :-)

Florian

--
Florian Effenberger <floeff@documentfoundation.org>
Steering Committee and Founding Member of The Document Foundation
Tel: +49 8341 99660880 | Mobile: +49 151 14424108
Skype: floeff | Twitter/Identi.ca: @floeff

--
Unsubscribe instructions: E-mail to mirrors+help@documentfoundation.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.documentfoundation.org/www/mirrors/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.