From: Ian Lance Taylor <iant@google.com>
To: overseers@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Don't let search bots look at buglist.cgi
Date: Fri, 13 May 2011 17:14:00 -0000 [thread overview]
Message-ID: <mcry62a7cau.fsf@coign.corp.google.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 570 bytes --]
I noticed that buglist.cgi was taking quite a bit of CPU time. I looked
at some of the long running instances, and they were coming from
searchbots. I can't think of a good reason for this, so I have
committed this patch to the gcc.gnu.org robots.txt file to not let
searchbots search through lists of bugs. I plan to make a similar
change on the sourceware.org and cygwin.com sides. Please let me know
if this seems like a mistake.
Does anybody have any experience with
http://code.google.com/p/bugzilla-sitemap/ ? That might be a slightly
better approach.
Ian
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: patch --]
[-- Type: text/x-diff, Size: 393 bytes --]
Index: robots.txt
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/robots.txt,v
retrieving revision 1.9
diff -u -r1.9 robots.txt
--- robots.txt 22 Sep 2009 19:19:30 -0000 1.9
+++ robots.txt 13 May 2011 17:08:33 -0000
@@ -5,4 +5,5 @@
User-Agent: *
Disallow: /viewcvs/
Disallow: /cgi-bin/
+Disallow: /bugzilla/buglist.cgi
Crawl-Delay: 60
next reply other threads:[~2011-05-13 17:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-13 17:14 Ian Lance Taylor [this message]
2011-05-16 9:45 ` Richard Guenther
2011-05-16 20:35 ` Ian Lance Taylor
2011-05-16 21:20 ` Joseph S. Myers
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=mcry62a7cau.fsf@coign.corp.google.com \
--to=iant@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=overseers@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).