From: Jonathan Larmour <jifl@jifvik.org>
To: Jim Meyering <jim@meyering.net>
Cc: overseers@sourceware.org
Subject: Re: high load average -> slow builds
Date: Tue, 15 Jan 2013 18:31:00 -0000 [thread overview]
Message-ID: <50F5A060.80003@jifvik.org> (raw)
In-Reply-To: <50F59F01.3000106@jifvik.org>
On 15/01/13 18:25, Jonathan Larmour wrote:
>
> Also:
> SENDER=gcc-bugzilla@gcc.gnu.org
> which implies bugzilla was the one sending the mail.
>
> Has the script got stuck, perhaps sending ever larger email in a loop? Or
> is someone abusing it?
Doh, I missed this obvious process in the 'ps' output:
bugzilla 25675 0.0 0.0 1356 284 ? S 17:31 0:00
bin/qmail-local -- bugzilla /sourceware/bugzilla bugzilla-gcc - gcc
sourceware.org gcc-bugzilla@gcc.gnu.org |bouncesaying "No forwarding
information (#5.2.1)"
So it looks a lot like someone (probably, inadvertently, a spammer) has
fabricated a mail which has caused gcc bugzilla's email interface to get
stuck in a loop of ever larger mails.
Whoever's managing the gcc bugzilla needs to a) work out how to kill it
off so it won't just restart, and b) fix (or report) this flaw in the
bugzilla email interface.
Jifl
--
--["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine
next prev parent reply other threads:[~2013-01-15 18:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-15 8:45 Jim Meyering
2013-01-15 18:25 ` Jonathan Larmour
2013-01-15 18:31 ` Jonathan Larmour [this message]
2013-01-15 18:36 ` Daniel Berlin
2013-01-15 21:18 ` Frank Ch. Eigler
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=50F5A060.80003@jifvik.org \
--to=jifl@jifvik.org \
--cc=jim@meyering.net \
--cc=overseers@sourceware.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).