qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: "Frédéric Grelot" <fredericg_99@yahoo.fr>
Cc: Rob Landley <rlandley@parallels.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu-git web viewer?
Date: Tue, 29 Mar 2011 08:21:12 -0500	[thread overview]
Message-ID: <4D91DCC8.4070400@codemonkey.ws> (raw)
In-Reply-To: <773c7347-4f36-480f-8d68-653673fb64f4@zimbra>

On 03/29/2011 06:58 AM, Frédéric Grelot wrote:
> See above mail, sent by Anthony yesterday :

My plan is to upgrade cgit later today FWIW.  If anyone has experience 
with other git front ends, I'd appreciate hearing about it.  Since 
qemu.org has pretty high traffic, I wanted something that cached 
aggressively.

Other than this current issue, I've had pretty good experiences with 
cgit so far.

Regards,

Anthony Liguori

>
>> We've been having problems on qemu.org all day.  Initially, it was
>> due
>> to a combination of a small DoS attack (not uncommon unfortunately).
>>
>> Later, the issue was observed when a crawler that was ignoring
>> robots.txt started indexing git.qemu.org.  We use cgit because of the
>> fact that it does aggressive caching but it also seems to frequently
>> SEGV leaving stale lock files.  This is causing all pages to be
>> dynamically generated which is an extremely slow path with cgit.
>>
>> For now, I've disabled cgit until I can try a newer version.  This
>> only
>> affects the web interface.  Pulling and pushing via the git:// or
>> ssh://
>> will continue to work.
>>
>> Regards,
>>
>> Anthony Liguori
>

      reply	other threads:[~2011-03-29 13:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-29 10:52 [Qemu-devel] qemu-git web viewer? Rob Landley
2011-03-29 11:58 ` Frédéric Grelot
2011-03-29 13:21   ` Anthony Liguori [this message]

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=4D91DCC8.4070400@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=fredericg_99@yahoo.fr \
    --cc=qemu-devel@nongnu.org \
    --cc=rlandley@parallels.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 NNTP newsgroup(s).