CentOS welcomes new mirror sites.
If you are considering setting up a public mirror site for CentOS please follow these guidelines to make sure that your mirror is consistent with the other mirror sites.
As a first step if you are not already subscribed, subscribe to the CentOS-mirror mailing list: http://lists.centos.org/mailman/listinfo/CentOS-mirror .
Public mirrors should syncronize 2-4 times per day and this should be run via cron. We highly recommend the use of lock files in your cron script so that you don\'t spawn multiple connections which is hard on our servers and on your mirror. If you don\'t know how to do this, please ask the list.
The best way to mirror the site inside of a cron job is:
rsync -aqzH --delete msync.centos.org::CentOS /path/to/local/mirror/root
EU users may wish to use eu-msync.centos.org::CentOS
US users may wish to use us-msync.centos.org::CentOS
(if you are using >= 2.6.4 version of rsync, you might want to specifiy the --delay-updates switch to the above line in your cron job)
Please email the list when you're all set up with your cron job and your initial sync is completed. We will add you to our list of mirror sites. Please provide all relevant URL's (ftp/http/rsync/?) as well as how often you are synchronizing the mirror network. Please include what city/state/country you are in and what your bandwidth cap is. Also please give a name and link to the sponsoring organization so we can give proper credit. If the best contact point for your mirror is not the address you are subscribed to the mailing list with, please provide the email address of your preferred contact as well.
Please alert the CentOS-mirror mailing list if anything about the server changes like location, available bandwidth, frequency of updates, etc.
We ask that Tier 2, personal, and company intranet mirror sites please pick a Tier 1 mirror rather than synchronizing directly from the master rsync server pool. We are not restricting the master rsync server pool in order to help new mirror sites get online expediently but will re-examine this issue if the master rsync server pool is overly used.
