Hi Alex
You can use CentOS master server bellow to sync your mirror:
msync.centos.org::CentOS [Official Full Master for CentOS]
eu-msync.centos.org::CentOS [EU users may wish to use] us-msync.centos.org::CentOS [US users may wish to use]
My own new server is now using msync.centos.org, speed is good enough!.
Command from My Corntab Entry:
41 01,07,13,19 * * * * /usr/bin/rsync -azqH --delete-before --partial --stats --bwlimit=1280 msync.centos.org::CentOS /storage/mirrors/linux/centos/ | mail -s "My CentOS mirror Status" centos-mirror-status@bauani.org
Using 10MB/s Pipe to sync with masters.
-- Ahamed Bauani Bangladesh Network Information Center http://www.bdnic.net/ http://www.bauani.org/
On Jan 13, 2008 11:36 PM, Alex Howells alex@bytemark.co.uk wrote:
Hi Guys,
It looks like the information on http://www.centos.org/modules/tinycontent/index.php?id=13 is a little dated. :( Would it be possible to get this updated please, or is it automatically generated and something I can influence from my end?
EU England Bytemark 4 5 i386 alpha x86_64 no HTTP FTP RSYNC
We currently mirror all the releases, but just for i386 and x86_64 architectures. Additionally we don't mirror .ISOs :)
You should be able to peek at what we mirror via; http://mirror.bytemark.co.uk/centos/
Additionally, could we please get access to your master mirror so we're not sync'ing off another Tier 1? Up until lately we were using Belnet but they've had some disk issues with their mirror recently and that kinda broke things :'(
If anyone notices anything wrong with the mirror, feel free to send me a message off-list and I'll look into things.
Kind Regards,
Alex Howells Bytemark Hosting _______________________________________________ CentOS-mirror mailing list CentOS-mirror@centos.org http://lists.centos.org/mailman/listinfo/centos-mirror
You can use CentOS master server bellow to sync your mirror:
eu-msync.centos.org::CentOS [EU users may wish to use]
We're using this one now, seems relatively nippy. We've been mirroring from either Belnet or HEAnet in the past; they're both pretty good.
#!/usr/bin/ruby def xsys(c); exit $? unless system(c); end
RSYNC = ENV['RSYNC'] RSYNC_MODULES = %w( CentOS ) RSYNC_HOST = "rsync://eu-msync.centos.org" RSYNC_DIR = ENV['MIRRORDIR']
options = [] options += %w( --exclude='.~tmp~/' --exclude='alpha/' --exclude='ia64/' --exclude='s390/' --exclude='s390x/' --exclude='isos/' --exclude='isos-dvd/' --exclude '*.iso' )
RSYNC_MODULES.each do |mod| cmdline = [RSYNC] cmdline += options cmdline << "#{RSYNC_HOST}/#{mod}" cmdline << "#{RSYNC_DIR}/centos" puts cmdline.join(" ") xsys("mkdir -p #{cmdline[-1]}") xsys(cmdline.join(" ")) end
# Pass 2 RSYNC_MODULES.each do |mod| cmdline = [RSYNC] cmdline += options cmdline += %w( --delete --delete-after --delete-excluded ) cmdline << "#{RSYNC_HOST}/#{mod}" cmdline << "#{RSYNC_DIR}/centos" p cmdline.join(" ") xsys(cmdline.join(" ")) end
Two-way mirror approach ensures that old content is only deleted after the fresh RPMs have been sync'd into the mirror.
It's invoked by a simple wrapper script through cron.
#!/bin/bash LIST=$* cd /mirror/scripts/sites
export MIRRORDIR="/mirror/public" export RSYNC="rsync --verbose --partial --progress --recursive --perms --times --links --safe-links --sparse --bwlimit=5120 --address=80.68.87.200"
for SCRIPT in $LIST ; do ./$SCRIPT done
I'm sure it's not perfect, but it does the trick :) Works especially well for things like Debian / Ubuntu, and you can handle distribution-specific things like architecture excludes using loops. Saves writing out a *huge* rsync command and maintaining it.
Alex