public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Jim Kingdon <kingdon@panix.com>
To: shebs@shebs.cnchost.com
Cc: overseers@sourceware.cygnus.com
Subject: Re: [Fwd: ftp probs]
Date: Tue, 20 Jun 2000 22:29:00 -0000	[thread overview]
Message-ID: <200006210529.BAA13670@panix3.panix.com> (raw)
Message-ID: <20000620222900.pLy7lXwetdexk5zdy0GhPV9W1d8M6C6aR8fumsd2Jj0@z> (raw)
In-Reply-To: <39504F15.461AA569@shebs.cnchost.com>

> Are there any plans to solve this?  When I go to test that the packages
> really are downloadable, I can never get on either... -s

People need to use mirrors (I'm trying to get sourceforge signed up as
a mirror but it might need to wait a few weeks until I'm working there
- I tried to send email, didn't get a response, and haven't pressed
the point).

As for mirrors being out of date, does the cygwin mirror polling
script test for up-to-date-ness?  Someone(TM) should look into what it
would take to use that script site-wide (to test for mirrors being up
even if it can't deal with staleness).

> I get a maximum download speed of about 500 bytes/sec, 
> with the connection dropping for minutes at a time.

I've been noticing this too (slow times from traceroute and web too).
It probably means that we need to restrict the number of anonymous FTP
users even further, although I haven't looked at the statistics lately.

The underlying issue, of course, is that sourceware's T1 is maxxed out
(see graphs and numbers at
http://sourceware.cygnus.com/sourceware/net.html ).

As I've said before (in some contexts in a half-joking manner), I
suspect VA might be willing to help somehow (with the sourceforge
mirror being the simplest way - I've already discussed that part with
them).  People who are planning to stay at Red Hat beyond 1 Jul will
need to think about what kinds of offers of help would be acceptable
to Red Hat, and what other solutions are possible.

I think I asked whether Apple had any interest in setting up a mirror.
Not justified based on xconq, I'm sad to say, but for GCC and
what-not.  Maybe that particular one isn't a good idea, but if
sourceware is really going to be a collaboration between various
companies, we need to figure out how to make that happen in a
financial sense.

I don't know, maybe just asking the right person (sysadmin? Kim?) in
Red Hat (with a case about how Red Hat customers rely on the site) is
all it would take.  But the nice thing about leaving is that I get to
seek another sucker for duties like that one :-).

  parent reply	other threads:[~2000-06-20 22:29 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 ` 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
2000-12-30  6:08 ` Jim Kingdon [this message]
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
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           ` 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  8:21             ` 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

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=200006210529.BAA13670@panix3.panix.com \
    --to=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).