From: DJ Delorie <dj@delorie.com>
To: jason-swarelist@molenda.com
Cc: cgf@cygnus.com, kingdon@panix.com, shebs@shebs.cnchost.com,
overseers@sourceware.cygnus.com
Subject: Re: [Fwd: ftp probs]
Date: Wed, 21 Jun 2000 07:54:00 -0000 [thread overview]
Message-ID: <200006211454.KAA11041@envy.delorie.com> (raw)
Message-ID: <20000621075400._8RzaVeXxFMZzBecnlfIs6LOxSpcNGWitU8XoBMh8gk@z> (raw)
In-Reply-To: <20000620235656.A28894@shell17.ba.best.com>
> Grope around /www/logs/ftp<something> - it's pretty clear.
21% of our ftp traffic is *snapshots* (about 2Gb/day). If each group
did snapshots half as often, it would reduce our ftp load by 10%.
Our top 30 FTP clients for the 10th-17th attached. Note that
Yggdrasil does full mirrors of sourceware, but I've had complaints
that it has a 10 user maximum! It also doesn't mirror right;
"lastest" is still a symlink. I'll send them a note.
224,412,100 wh4036.stw.uni-rostock.de
227,370,945 archive.threeweb.ad.jp
235,302,855 nephtys.lip6.fr
263,295,217 ccftp.kpprc.edu.tw
297,557,102 210.77.38.126 (in cnc.ac.cn somewhere)
373,046,918 ftp.jaist.ac.jp
377,356,047 sysg.kek.jp
398,887,710 203-165-64-57.sugnm1.kt.home.ne.jp
419,318,464 netserv2.chg.ru
484,886,139 kepler.mirror.ac.uk
493,323,342 swallow
493,933,460 prx1.commerzbank.com
545,111,124 u6117.seaple.icc.ne.jp
553,389,538 203-165-64-79.sugnm1.kt.home.ne.jp
554,374,570 altay.adm.deu.edu.tr
597,926,849 swiss1.fw-bc.sony.com
608,625,473 ftpsv1.u-aizu.ac.jp
626,512,801 Venus.buyingsources.com
676,789,845 compton.mirror.ac.uk
729,746,782 pine.ict.nsk.su
763,177,919 206.153.39.108 (in racsa.co.cr somewhere)
839,094,832 polar.lerc.nasa.gov
879,603,531 202.181.240.186 (in cubix.net somewhere)
923,427,993 eufrat.pvv.ntnu.no
931,281,969 wizard.freesoftware.com
952,943,148 ftp1.sinica.edu.tw
959,735,851 ftp.unina.it
965,826,867 nic.funet.fi
1,371,216,531 freya.yggdrasil.com
2,402,662,730 206.153.39.110 (in racsa.co.cr somewhere)
next prev parent reply other threads:[~2000-06-21 7:54 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-30 6:08 Stan Shebs
2000-06-20 22:05 ` Stan Shebs
2000-12-30 6:08 ` Jim Kingdon
2000-06-20 22:29 ` Jim Kingdon
2000-12-30 6:08 ` Chris Faylor
2000-06-20 22:38 ` Chris Faylor
2000-12-30 6:08 ` Jason Molenda
2000-06-20 23:57 ` Jason Molenda
2000-12-30 6:08 ` DJ Delorie [this message]
2000-06-21 7:54 ` DJ Delorie
2000-12-30 6:08 ` Chris Faylor
2000-06-21 8:00 ` Chris Faylor
2000-12-30 6:08 ` DJ Delorie
2000-06-21 8:19 ` DJ Delorie
2000-12-30 6:08 ` Jason Molenda
2000-06-21 0:09 ` Jason Molenda
2000-12-30 6:08 ` Gerald Pfeifer
2000-06-21 8:11 ` Gerald Pfeifer
2000-12-30 6:08 ` DJ Delorie
2000-06-21 8:21 ` DJ Delorie
2000-12-30 6:08 ` Jeffrey A Law
2000-06-21 8:30 ` Jeffrey A Law
2000-12-30 6:08 ` DJ Delorie
2000-06-21 8:39 ` DJ Delorie
2000-12-30 6:08 ` Gerald Pfeifer
2000-06-22 14:12 ` Gerald Pfeifer
2000-12-30 6:08 ` DJ Delorie
2000-06-21 7:13 ` DJ Delorie
2000-12-30 6:08 ` DJ Delorie
2000-06-21 7:11 ` DJ Delorie
2000-12-30 6:08 ` Chris Faylor
2000-06-20 22:13 ` Chris Faylor
2000-12-30 6:08 ` Jeffrey A Law
2000-06-21 8:47 ` Jeffrey A Law
2000-12-30 6:08 ` Jim Kingdon
2000-06-20 22:36 ` Jim Kingdon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200006211454.KAA11041@envy.delorie.com \
--to=dj@delorie.com \
--cc=cgf@cygnus.com \
--cc=jason-swarelist@molenda.com \
--cc=kingdon@panix.com \
--cc=overseers@sourceware.cygnus.com \
--cc=shebs@shebs.cnchost.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).