All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Kay Sievers <kay.sievers@vrfy.org>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: gitweb.cgi
Date: Wed, 19 Oct 2005 09:16:44 -0700	[thread overview]
Message-ID: <4356716C.7080003@zytor.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0510190655230.3369@g5.osdl.org>

Linus Torvalds wrote:
> 
> Well, I tried again this morning, and _boy_ is it better. The "projects" 
> thing came up immediately, no waiting. 
> 
> Maybe it just took a while for the mod_cache thing to take effect as 
> Apache swarm members time out? 
> 

No, that's not it.  It takes killing httpd and restarting it.  Rather, 
it looks like mod_cache in different swarm members doesn't always 
communicate instantly, which is also underscored by the fact that cache 
files don't appear into the filesystem until after a while.

	-hpa

  reply	other threads:[~2005-10-19 16:17 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-18  2:57 gitweb.cgi H. Peter Anvin
2005-10-18 11:07 ` gitweb.cgi Kay Sievers
2005-10-18 16:52   ` gitweb.cgi H. Peter Anvin
2005-10-18 17:24   ` gitweb.cgi H. Peter Anvin
2005-10-18 20:44     ` gitweb.cgi Brian Gerst
2005-10-19  0:27     ` gitweb.cgi Linus Torvalds
2005-10-19  0:30       ` gitweb.cgi H. Peter Anvin
2005-10-19  0:53         ` Optimize common case of git-rev-list (was Re: gitweb.cgi) Linus Torvalds
2005-10-19  0:38       ` gitweb.cgi H. Peter Anvin
2005-10-19  1:02         ` gitweb.cgi Linus Torvalds
2005-10-19  1:14           ` gitweb.cgi H. Peter Anvin
2005-10-19 13:59             ` gitweb.cgi Linus Torvalds
2005-10-19 16:16               ` H. Peter Anvin [this message]
2005-10-19  1:23           ` gitweb.cgi Kay Sievers
2005-10-19  1:33     ` gitweb.cgi Kay Sievers

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=4356716C.7080003@zytor.com \
    --to=hpa@zytor.com \
    --cc=git@vger.kernel.org \
    --cc=kay.sievers@vrfy.org \
    --cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.