mirror.megahappy.net
ipv4 and ipv6, currently only http. Will add rsync later.
This is my shell box I use to get on IRC. That's about all it does so I thought I'd give it something else to do.
Connection is 100MBit, If I use over 10TB of bandwidth per month then my 100MBit connection is reduced to 10MBit. Besides that it is unmetered. Since it is basically my IRC shell account - I'm totally ok with always having 10Mbit connection.
Crontab is setup to sync 4 times per day. everything is in sync now.
Org credit: jiqiren on Freenode (or just Anonymous)
-Bryan
On 23.03.2013 00:38, Bryan Whitehead wrote:
mirror.megahappy.net
ipv4 and ipv6, currently only http. Will add rsync later.
This is my shell box I use to get on IRC. That's about all it does so I thought I'd give it something else to do.
Connection is 100MBit, If I use over 10TB of bandwidth per month then my 100MBit connection is reduced to 10MBit.
That might be okay for you, it is not okay for us (especially as there are loads of mirrors in the US having no cap). That is nothing personal, I just don't want people to suddenly run into that 10Mbit cap, while there are other mirrors around which can deliver 100 to 1000Mbit/s.
Why not join the torrent swarm with that box? This way it doesn't really matter which speed your connection is at (and you can shape it any way you like).
Regards,
Ralph
That might be okay for you, it is not okay for us (especially as there are loads of mirrors in the US having no cap). That is nothing personal, I just don't want people to suddenly run into that 10Mbit cap, while there are other mirrors around which can deliver 100 to 1000Mbit/s.
This is for a mirror in Germany, not the US.
That said, it would be great if the howto was more clear about minimum network requirements (even better would be an expected network traffic statement). I wouldn't have gone though the trouble of setting this up if I knew the possibility of 10Mbit connection being too little was a problem.
On 25.03.2013 01:12, Bryan Whitehead wrote:
That might be okay for you, it is not okay for us (especially as there are loads of mirrors in the US having no cap). That is nothing personal, I just don't want people to suddenly run into that 10Mbit cap, while there are other mirrors around which can deliver 100 to 1000Mbit/s.
This is for a mirror in Germany, not the US.
That said, it would be great if the howto was more clear about minimum network requirements (even better would be an expected network traffic statement). I wouldn't have gone though the trouble of setting this up if I knew the possibility of 10Mbit connection being too little was a problem.
Yeah, sorry, I'll update the page. Another possibility would be to add you to the "lower" mirror list, which doesn't get any traffic via our mirrorlist, but will show up on the mirror page (we have around ten of those).
Regards,
Ralph
We have seen a sudden fall in traffic on our mirror from 20th March onward. Any particular reason ? We used to see about 50-100 GB transfer a day, and now its just about a few MB.
-Shaunak Sayta hostingxtreme.com
On Fri, Mar 22, 2013 at 4:38 PM, Bryan Whitehead driver@megahappy.netwrote:
mirror.megahappy.net
ipv4 and ipv6, currently only http. Will add rsync later.
This is my shell box I use to get on IRC. That's about all it does so I thought I'd give it something else to do.
Connection is 100MBit, If I use over 10TB of bandwidth per month then my 100MBit connection is reduced to 10MBit. Besides that it is unmetered. Since it is basically my IRC shell account - I'm totally ok with always having 10Mbit connection.
Crontab is setup to sync 4 times per day. everything is in sync now.
Org credit: jiqiren on Freenode (or just Anonymous)
-Bryan _______________________________________________ CentOS-mirror mailing list CentOS-mirror@centos.org http://lists.centos.org/mailman/listinfo/centos-mirror
Hi,
On 25.03.2013 19:05, HostingXtreme wrote:
We have seen a sudden fall in traffic on our mirror from 20th March onward. Any particular reason ? We used to see about 50-100 GB transfer a day, and now its just about a few MB.
a) please don't hijack other people's threads.
b) (This is from today):
http://centos.hostingxtreme.com/5.9/extras/i386/repodata/repomd.xml - 403 Forbidden http://centos.hostingxtreme.com/5.9/contrib/i386/repodata/repomd.xml - 403 Forbidden http://centos.hostingxtreme.com/5.9/cr/i386/repodata/repomd.xml - 403 Forbidden http://centos.hostingxtreme.com/5.9/contrib/x86_64/repodata/repomd.xml - 403 Forbidden http://centos.hostingxtreme.com/5.9/centosplus/i386/repodata/repomd.xml - 403 Forbidden http://centos.hostingxtreme.com/5.9/os/x86_64/repodata/repomd.xml - 403 Forbidden http://centos.hostingxtreme.com/5.9/contrib/x86_64/repodata/repomd.xml error from cache 403 Forbidden http://centos.hostingxtreme.com/5.9/updates/i386/repodata/repomd.xml - 403 Forbidden http://centos.hostingxtreme.com/5.9/fasttrack/i386/repodata/repomd.xml - 403 Forbidden http://centos.hostingxtreme.com/5.9/os/i386/repodata/repomd.xml - 403 Forbidden http://centos.hostingxtreme.com/5.9/os/x86_64/repodata/repomd.xml error from cache 403 Forbidden http://centos.hostingxtreme.com/6.3/addons/i386/repodata/repomd.xml - 500 Can't connect to centos.hostingxtreme.com:80 (connect: timeout)
Looks like the 403 URLs work again, so it should be in the mirrorlists again soon.
Regards,
Ralph
-
Bryan Whitehead -
HostingXtreme -
Ralph Angenendt