Apropos -- we're seeing the same issue. We presently use Apache as our server, but even it doesn't seem to be able to prevent the use of download accelerators, or if it can, I'm not smart enough to figure out how. How are other mirrors dealing with this problem?
(In our case we probably wouldn't care if the mirror had enough memory to keep everything in RAM, but it doesn't, so downloading a DVD iso in ten simultaneous pieces causes ten simultaneous random accesses on the disk, and that's not cool.)
-- Toivo Voll Data Network Management Academic Computing University of South Florida -----Original Message----- From: centos-mirror-bounces@centos.org [mailto:centos-mirror-bounces@centos.org] On Behalf Of sukru@cs.hacettepe.edu.tr Sent: Wednesday, April 25, 2007 04:29 To: centos-mirror@centos.org Subject: [CentOS-mirror] our mirror address
[8<]
A few months earlier we'd decided to limit HTTP access to all our mirrors to internal machines only. This was done because we could throttle FTP connections while there was no viable was to prevent abuse of HTTP ones (we'd several problems due to people downloading with 10+ threads in parallel).
[>8]