public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Jeffrey A Law <law@cygnus.com>
To: shebs@shebs.cnchost.com
Cc: overseers@sourceware.cygnus.com
Subject: Re: ftp load
Date: Tue, 14 Mar 2000 08:45:00 -0000	[thread overview]
Message-ID: <7702.953051937@upchuck> (raw)
Message-ID: <20000314084500.wavst-1DmR93UIGt97t8tVnCBi3Qoi7hPyP0nWmPT20@z> (raw)
In-Reply-To: <38CE6B44.33DCDE6D@shebs.cnchost.com>

  In message < 38CE6B44.33DCDE6D@shebs.cnchost.com >you write:
  > OK, so while it's nice that some projects have lots of mirrors
  > to redirect people, my little Xconq project doesn't have that;
  > so when the ftp connections are maxed out, nobody can get to
  > my just-released development version.  They seem to be maxed-out
  > all the time now - what's going on, and is this going to change?
It is believed we are saturating the dedicated T1 for the sourceware
machine, so we've throttled the FTP connections (again).

The best thing to do is to get some mirrors :-)  You might even have some
that you're not aware of (a number of sites appear to just mirror everything
on sourceware they can find).  It might be worth a little time to scan the
mirror list and see which are mirroring xconq.

As for long term plans, there has been talk of co-locating sourceware, but
it hasn't progressed beyond "just talk" yet.

It would be nice if we had the capability to limit connections on a
per-project basis.  But I don't think we have that kind of capability
right now.
jeff

  parent reply	other threads:[~2000-03-14  8:45 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-30  6:08 Stan Shebs
2000-03-14  8:32 ` Stan Shebs
2000-12-30  6:08 ` Jeffrey A Law [this message]
2000-03-14  8:45   ` Jeffrey A Law
2000-12-30  6:08   ` Mark Galassi
2000-03-14 10:43     ` Mark Galassi
2000-12-30  6:08   ` Jim Kingdon
2000-03-14 13:56     ` Jim Kingdon
2000-12-30  6:08     ` Bart Veer
2000-03-15  3:29       ` Bart Veer
2000-12-30  6:08       ` Chris Faylor
2000-03-15  5:38         ` Chris Faylor
2000-12-30  6:08         ` Jim Kingdon
2000-03-15  6:26           ` Jim Kingdon
2000-12-30  6:08           ` Chris Faylor
2000-03-15  6:30             ` Chris Faylor
2000-12-30  6:08             ` Jim Kingdon
2000-03-15  6:46               ` Jim Kingdon
2000-12-30  6:08               ` Chris Faylor
2000-03-15  7:00                 ` Chris Faylor
2000-12-30  6:08     ` Jason Molenda
2000-03-14 14:20       ` Jason Molenda
2000-12-30  6:08   ` Chris Faylor
2000-03-14  9:35     ` Chris Faylor
2000-12-30  6:08     ` Bart Veer
2000-03-14  9:42       ` Bart Veer
2000-12-30  6:08 Louis Stone-Collonge
2000-03-21 22:14 ` Louis Stone-Collonge
2000-12-30  6:08 ` Jim Kingdon
2000-03-22  6:49   ` Jim Kingdon
2000-12-30  6:08   ` Stan Shebs
2000-03-23  8:32     ` Stan Shebs
2000-12-30  6:08 ` 'Chris Faylor'
2000-03-21 22:17   ` 'Chris Faylor'

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=7702.953051937@upchuck \
    --to=law@cygnus.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).