Olleg Samoylov wrote:
> Josip Rodin wrote:
>> You can optimize that further, by doing a two stage sync.
>> More exactly, like this:
>>
>> rsync --recursive --times --links --hard-links \
>> --exclude "Packages*" --exclude "Sources*" \
>> --exclude "Release*" --exclude "ls-lR*" \
>> --verbose --stats \
>> $FROM $TO > $LOGFILE 2>&1
>>
>> rsync --recursive --times --links --hard-links --max-delete=40000 \
>> --delete --delete-after \
>> --exclude "Archive-Update-in-Progress-${HOSTNAME}" \
>> --exclude "project/trace/${HOSTNAME}" \
>> --verbose --stats \
>> $FROM $TO > $LOGFILE.2nd 2>&1
>
> Why do you still use two stage rsync? AFAIK the same effect can be
> reached with options like --delete-after --delay-updates in one stage.
>
out the top of my head,
delay-updates doesn't update the pool before the package listing, so there is still a time
window with updated packages files without a updates pool, because the update isn't an
atomic operation.
so first updating the pool with new packages, then updating the packages listings, and
then deleting old files is the way to prevent that kind of windows with broken mirrors.
ofcourse i could be wrong ;-)
regards
Robbert Muller
Attachment:
signature.asc
Description: OpenPGP digital signature