From: Jason Molenda <jason-swarelist@molenda.com>
To: Chris Faylor <cgf@cygnus.com>
Cc: Jim Kingdon <kingdon@panix.com>,
shebs@shebs.cnchost.com, overseers@sourceware.cygnus.com,
DJ Delorie <dj@cygnus.com>
Subject: Re: [Fwd: ftp probs]
Date: Wed, 21 Jun 2000 00:09:00 -0000 [thread overview]
Message-ID: <20000621000908.A1041@shell17.ba.best.com> (raw)
Message-ID: <20000621000900.QxirMfERBCV6gSuIIf5q6Aq8YNg4h-OQcve93yuOF4M@z> (raw)
In-Reply-To: <20000620235656.A28894@shell17.ba.best.com>
(real quick ... )
On Tue, Jun 20, 2000 at 11:56:56PM -0700, Jason Molenda wrote:
> There are only three solutions. [...]
OK, four/five - move gcc/cygwin to sourceforge or gnu.org.
Six (I forgot about this) - set up multiple IP#s on sourceware.
1 for sourceware, 1 for gcc.gnu.org, 1 for cygwin.cygnus.com.
I believe wuftpd or proftpd can support virtual hosts when multiple
IP#s are present, so you can require someone to go to ftp://gcc.gnu.org
to get access to /pub/gcc and ftp://cygwin.cygnus.com to get access
to /pub/cygwin. Allow only mirror sites to have access to those two
'ftp sites', and ease/drop restrictions on the sourceware 'ftp site'.
The problem is entirely with gcc/cygwin - reduce the ftp load of those
two (both of which have extensive mirroring networks) and the bandwidth
problems evaporate.
FWIW I occasionally read some mailing list archives via the web on
sourceware, and I can also attest that the bandwidth has gone to
crap, especially of late.
Jason
next prev parent reply other threads:[~2000-06-21 0:09 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
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 [this message]
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 ` Gerald Pfeifer
2000-06-22 14:12 ` Gerald Pfeifer
2000-12-30 6:08 ` DJ Delorie
2000-06-21 8:39 ` DJ Delorie
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 ` Jim Kingdon
2000-06-20 22:36 ` Jim Kingdon
2000-12-30 6:08 ` Jeffrey A Law
2000-06-21 8:47 ` Jeffrey A Law
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=20000621000908.A1041@shell17.ba.best.com \
--to=jason-swarelist@molenda.com \
--cc=cgf@cygnus.com \
--cc=dj@cygnus.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).