[mirror-admin] master server sync stats and recommendations

[Chris Adams]

Once upon a time, Axel Thimm <Axel.Thimm at ATrpms.net> said:
> Aside from buggy null-updates from the server side, what if you want a
> pure rsync solution, do we want to start mixing protocols?
> it more granular helps as well, unless we only target fedora-enchilada
> consumers.

Well, if you are going to look at the content of a "last updated" file,
or compare its timestamp to something, your aren't pure rsync already
(you'll have to have some scripting, be it shell, perl, python, etc.).
Also, since you should have some type of locking to prevent overlapping
rsyncs, you should have some type of scripting already.

As far as fetching the timestamp via HTTP HEAD: well, we are HTTP
mirrors after all.  The only time this would be a problem would be if
there is a new rsync module that is not public, but that has not
happened to date (so I don't think it is a concern).

I do think it would be reasonable to have a fullfilelist at the top of
each rsync module (even though the modules are nested).
-- 
Chris Adams <cmadams at hiwaay.net>
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.

--