Just as an aside: This is an excellent time to implement a lock file system. As it says on the mirror site,
"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."
Lock files are a good thing (tm). I'm sure there's a better way to do it, but I'm doing the following:
if [ -f /some/path/lockfile ] then exit fi touch /some/path/lockfile rsync -blah -blah us-msync.centos.org::CentOS /my/mirror rm -f /some/path/lockfile
~Will Virginia Tech CS dept techstaff
Johnny Hughes wrote:
On Fri, 2006-03-17 at 13:31 +0100, Lars Bruno Hansen wrote:
hey guys,
Quick heads up - CentOS 4.3 is going to open upto rsync during the course of today, you might want to make sure that drive space issues, network issues etc are all sorted out before then.
4.3 is only going to be available via msync.centos.org - and NOT mirror.centos.org, so make sure you rsync's are pointing to the correct location - in some cases, it might be better to use another rsync mirror close to you, rather than the centos.org network, to ensure faster prorogation.
Either Johnny or I will post to the mailing list, before the /4/ symlink moves over from /4.2 tree to the /4.3 tree ( and therefore the user end traffic ).
Hi Karanbir,
How much extra diskspace is needed, the 4.2 is 30G, should one have at least 30G free diskspace,
That is about right for this one too ... but after all arches are released and all the external mirror syncs are done, we will move the 4.2 tree into the vault ...
Then the size should shrink back down to be similar to now for the overall mirror.
CentOS-mirror mailing list CentOS-mirror@centos.org http://lists.centos.org/mailman/listinfo/centos-mirror