URLs: http://mirror.umoss.org/centos/ & rsync://mirror.umoss.org/centos/ Location: College Park, MD, USA Bandwidth: Up to 100 Mbps; 1 Gbps available to academic network users Organization: University of Maryland, College Park / http://www.umd.edu/
(This replaces the CentOS mirror that was available at http://mirror.rhsmith.umd.edu/)
Am 14.03.10 21:36, schrieb UMOSS:
URLs: http://mirror.umoss.org/centos/ & rsync://mirror.umoss.org/centos/ Location: College Park, MD, USA Bandwidth: Up to 100 Mbps; 1 Gbps available to academic network users Organization: University of Maryland, College Park / http://www.umd.edu/
Who is the contact for that? The same as
(This replaces the CentOS mirror that was available at http://mirror.rhsmith.umd.edu/)
?
Same archs/releases as before?
Regards,
Ralph
The contact for mirror.umoss.org should be mirror@umoss.org. This mirror has all architectures for releases 4(.0) and up.
On Tue, 16 Mar 2010 23:46:45 +0100, Ralph Angenendt ralph.angenendt@gmail.com wrote:
Am 14.03.10 21:36, schrieb UMOSS:
URLs: http://mirror.umoss.org/centos/ &
rsync://mirror.umoss.org/centos/
Location: College Park, MD, USA Bandwidth: Up to 100 Mbps; 1 Gbps available to academic network users Organization: University of Maryland, College Park /
Who is the contact for that? The same as
(This replaces the CentOS mirror that was available at http://mirror.rhsmith.umd.edu/)
?
Same archs/releases as before?
Regards,
Ralph _______________________________________________ CentOS-mirror mailing list CentOS-mirror@centos.org http://lists.centos.org/mailman/listinfo/centos-mirror
We currently update our public mirror from one other mirror site because that site has the DVD ISOs, which we want, and the site is also on Internet2. This works well for us except if there is an issue with the other mirror. How do the rest of you handle rsync'ing from multiple mirrors? I can think of a few ways to handle it, but none of my approaches seem to be very elegant.
Thanks for any tips.
Jess
P.S. Forgive me if this has already been addressed on the list. I searched some of the mailing list archives, but did not find what I was looking for.
On Wed, 17 Mar 2010, Jess Cannata wrote:
We currently update our public mirror from one other mirror site because that site has the DVD ISOs, which we want, and the site is also on Internet2. This works well for us except if there is an issue with the other mirror. How do the rest of you handle rsync'ing from multiple mirrors? I can think of a few ways to handle it, but none of my approaches seem to be very elegant.
Thanks for any tips.
Jess
P.S. Forgive me if this has already been addressed on the list. I searched some of the mailing list archives, but did not find what I was looking for.
I can think of two approaches:
1) sync from server1 (without using --delete), then sync from server2 (with --delete). The downsides of this are that you're always churing through two mirrors, and that, if server1 has something new before server2, the sync from server2 would delete the new content.
2) Use an "or" in your sync. This would only trigger the sync from server2 if the sync from server1 fails. This option would be much less likely to ping-pong on new content.
DR
On 03/17/2010 04:49 PM, David Richardson wrote:
On Wed, 17 Mar 2010, Jess Cannata wrote:
We currently update our public mirror from one other mirror site because that site has the DVD ISOs, which we want, and the site is also on Internet2. This works well for us except if there is an issue with the other mirror. How do the rest of you handle rsync'ing from multiple mirrors? I can think of a few ways to handle it, but none of my approaches seem to be very elegant.
Thanks for any tips.
Jess
P.S. Forgive me if this has already been addressed on the list. I searched some of the mailing list archives, but did not find what I was looking for.
I can think of two approaches:
- sync from server1 (without using --delete), then sync from server2
(with --delete). The downsides of this are that you're always churing through two mirrors, and that, if server1 has something new before server2, the sync from server2 would delete the new content.
- Use an "or" in your sync. This would only trigger the sync from server2
if the sync from server1 fails. This option would be much less likely to ping-pong on new content.
DR
Thanks for the ideas.
Jess
Am 14.03.10 21:36, schrieb UMOSS:
URLs: http://mirror.umoss.org/centos/ & rsync://mirror.umoss.org/centos/ Location: College Park, MD, USA Bandwidth: Up to 100 Mbps; 1 Gbps available to academic network users Organization: University of Maryland, College Park / http://www.umd.edu/
Okay, added. Should show up soon.
Thanks for supporting us.
Ralph
-
David Richardson -
Jess Cannata -
Ralph Angenendt -
UMOSS