[mirror-admin] push mirroring plans

[Ricky Zhou]

On 2008-12-17 01:23:32 PM, Chuck Anderson wrote:
> See my other email in this thread about what is essentially a 
> "TIMESTAMP" file.  The issue I see with this is that unless mirror 
> admins are very careful to update the checksum/timestamp file 
> separately after a regular sync is complete, we can end up with a 
> situation where a downstream mirror thinks version X is up and ready 
> but in reality it is only partially synced.  Everybody should be using 
> --delay-updates, but...
The timestamp file suggestion is the most elegant method I've heard so
far, because it checks not only that new content is available, but also
that the upstream mirror has that content (assuming they used
--delay-updates).  Since this doesn't require querying mirrormanager,
it works even if upstream isn't using report_mirror or talking to
mirrormanager at all.

Thanks,
Ricky
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
Url : http://mail.ale.org/pipermail/mirror-admin/attachments/20081230/7821ff7c/attachment.bin 
-------------- next part --------------
--