From: Michael Elizabeth Chastain <mec@shout.net>
To: jason-gcclist@molenda.com, rschiele@uni-mannheim.de
Cc: cvs-hackers@gnu.org, gcc@gcc.gnu.org, hp@bitrange.com,
overseers@gcc.gnu.org
Subject: Re: cvs corrruption in gcc/unroll.c
Date: Sun, 09 Mar 2003 06:31:00 -0000 [thread overview]
Message-ID: <200303090631.h296VHJ12877@duracef.shout.net> (raw)
First, an explanation of why anonymous cvs on subversions has been
slow/broken for the past few days. This is from the front page of
savannah.gnu.org:
Latest News
Server exhausted, mldonkey clients charged
yeupou - Fri 03/07/03 at 05:27 - 3 messages
The Savannah server is currently exhausted because hundred of mldonkey
clients are trying to download differents files as servers-list or
motd (server.met, motd.html, motd.conf, peers.ocl).
Despite the fact that we now fordib access to this kind of data, it
still creates tons of http connections and generates lot of CPU usage.
mldonkey is a p2p program developed as a savannah project. A recent
release of mldonkey contained savannah URL's for its configuration
files, so myriads of mldonkey users are pounding the servers for its
configuration files. (Literally: one 'myriad' is 10,000, and they
are seeing about 100,000 connections per day from mldonkey users).
I'm just mentioning this because it's relevant news and nobody else
has mentioned it yet. I don't want to start a big off-topic thread
about it.
My armchair guess, as an outside amateur kind of guy, is that
gcc.gnu.org is fine and that subversions.gnu.org is suffering some
thrashing-induced corruption.
Michael C
next reply other threads:[~2003-03-09 6:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-09 6:31 Michael Elizabeth Chastain [this message]
[not found] <20030308234157.GA30916@schiele.local>
2003-03-08 23:45 ` Hans-Peter Nilsson
2003-03-09 0:10 ` Robert Schiele
2003-03-09 0:19 ` Jason Molenda
2003-03-09 0:38 ` Robert Schiele
2003-03-09 2:55 ` Jason Molenda
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=200303090631.h296VHJ12877@duracef.shout.net \
--to=mec@shout.net \
--cc=cvs-hackers@gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=hp@bitrange.com \
--cc=jason-gcclist@molenda.com \
--cc=overseers@gcc.gnu.org \
--cc=rschiele@uni-mannheim.de \
/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).