public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: fche@redhat.com (Frank Ch. Eigler)
To: octoploid <cryptooctoploid@gmail.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Bugzilla down
Date: Thu, 06 Oct 2011 22:18:00 -0000	[thread overview]
Message-ID: <y0md3e9j09j.fsf@fche.csb> (raw)
In-Reply-To: <loom.20111006T170939-641@post.gmane.org> (cryptooctoploid@gmail.com's message of "Thu, 6 Oct 2011 15:13:14 +0000 (UTC)")

octoploid <cryptooctoploid@gmail.com> writes:

>> Actually, the whole gcc.gnu.org since yesterday seems rather flaky. At 
>> the moment it works fine for me, though.
>
> Same symptoms as those on kernel.org 

In gcc.gnu.org's case, apparently this was being caused by someone
hammering on the bugzilla server.  A case of excessive popularity
perhaps rather than anything too suspicious.

> before the intrusion was detected.  Perhaps someone should run
> chkrootkit on the gnu servers?

This is being regularly done already.

- FChE

  reply	other threads:[~2011-10-06 21:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-06 14:48 Paulo J. Matos
2011-10-06 15:23 ` Paolo Carlini
2011-10-06 16:43   ` octoploid
2011-10-06 22:18     ` Frank Ch. Eigler [this message]
2011-10-06 15:55 ` Paulo J. Matos

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=y0md3e9j09j.fsf@fche.csb \
    --to=fche@redhat.com \
    --cc=cryptooctoploid@gmail.com \
    --cc=gcc@gcc.gnu.org \
    /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).