Bogdan Costescu wrote:
Building the metadata is only one part of the problem, getting it into
sync with all the mirrors in a reasonable manner is another issue.
CentOS does it right (or at least well enough that we, users, don't
notice). Not wanting to imply anything, except that it's possible :-)
The way CentOS does it - is to isolate the first two tiers of mirrors
from the the users, completely. The third tier sync's from this second
tier every 10 minutes - and does so on very high speed links. Links that
we control and policy that we can enforce.
RPMForge and the its mirrors dont quite work like that. And while I have
a fairly decent idea as to what is going on with the master machine, I
am not 100% clear on how that peculates down to the mirrors. Dag did
explain it to me, and it made perfect sense at the time. However, I must
be getting old.
Because in my mind this issue and the time needed to actually update the
repo are somehow related; see Dag's post about timing:
http://lists.rpmforge.net/pipermail/users/2008-September/001861.html
I missed that post from dag, and am really not sure why things would
take 8 hrs.
--
Karanbir Singh : http://www.karan.org/ : [EMAIL PROTECTED]
_______________________________________________
users mailing list
[email protected]
http://lists.rpmforge.net/mailman/listinfo/users
