On 16/09/2017 10:32, Peter Palfrader wrote:
On Fri, 15 Sep 2017, Arnaud Abélard wrote:
All our debian mirrors (main, cdroms, security, backports and non-US) are
now using ftpsync and should be up to date.
I don't know much about the cdimage mirroring process. I don't think
ftpsync is well suited for that.
Also, the backports tree is obsolete for a few years now (the service is
part of the main debian tree since wheezy), and non-US is obsolete for
well over a decade. You might want to retire these mirrors.
I got rid of the backports and nonUS mirrors that were still running for
"historical" reasons...
(Furthermore, we don't recommend security mirrors being used, and thus
don't think security should be mirrored, but that's your call.)
I've kept this one as all our servers are referencing it, but we'll keep
in mind this might not be optimal.
How often does your sync process run for the main archive? We recommend
4 times a day to match the update frequency of the debian archive. If
you want to match that frequency, options include:
- cron this, picking a time when you think your upstream would usually
be done with their mirrorrun, or
I cron'ed the mirrors to every 6 hours. That should do the job.
Thanks again.
Arnaud
- use ftpsync-cron (in the ftpsync released a few days ago), which is a
script that should be run out of cron every 30-60 minutes and which
checks the upstream's tracefile for whether a mirror run happened and
if it did, runs one locally
- set up ssh triggers with your upstream.
Cheers,
--
Arnaud Abélard
jabber: arnaud.abel...@univ-nantes.fr / twitter: ArnY
Administrateur Système
DSI Université de Nantes
-
