From: Jeff King <peff@peff.net>
To: Brian Gernhardt <brian@gernhardtsoftware.com>
Cc: "git@vger.kernel.org List" <git@vger.kernel.org>
Subject: Re: HTTP tests fail on OS X
Date: Fri, 21 Jun 2013 14:03:34 -0400 [thread overview]
Message-ID: <20130621180334.GA4499@sigill.intra.peff.net> (raw)
In-Reply-To: <D0852D0F-3282-41DF-8A5A-4BEF1B39ED66@gernhardtsoftware.com>
On Fri, Jun 21, 2013 at 01:03:40PM -0400, Brian Gernhardt wrote:
> On Jun 21, 2013, at 12:49 AM, Jeff King <peff@peff.net> wrote:
>
> > I'm not sure what else to look at...I guess try ratcheting up the
> > debugging/log level on your failing copy and see if it prints anything
> > useful.
>
> I found this error in the error.log:
>
> [Fri Jun 21 12:59:59 2013] [emerg] (2)No such file or directory: Couldn't create accept lock (/private/var/run/accept.lock.64288) (5)
Hmm. I am far from an apache expert, but I believe that is what would
happen if the LockFile directive was not there at all. IOW, it seems
like your apache is treating "<IfVersion < 2.4>" as false. Which seems
weird to me.
It's possible I'm using IfVersion wrong, though it does seem to work for
me elsewhere.
IfVersion comes from mod_version. I assume that if it were not loaded,
apache would complain about the directive entirely. But it's true that
we don't load it until later. Maybe try moving the IfVersion/Lockfile
stanza down below the mod_version LoadModule line?
-Peff
next prev parent reply other threads:[~2013-06-21 18:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-21 4:27 HTTP tests fail on OS X Brian Gernhardt
2013-06-21 4:30 ` Jeff King
2013-06-21 4:42 ` Jeff King
2013-06-21 4:45 ` Brian Gernhardt
2013-06-21 4:49 ` Jeff King
2013-06-21 17:03 ` Brian Gernhardt
2013-06-21 18:03 ` Jeff King [this message]
2013-06-21 18:08 ` Brian Gernhardt
2013-06-21 18:12 ` [PATCH] lib-httpd/apache.conf: check version only after mod_version loads Jeff King
2013-06-21 18:15 ` Brian Gernhardt
2013-06-21 18:18 ` Jeff King
2013-06-21 20:59 ` Junio C Hamano
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=20130621180334.GA4499@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=brian@gernhardtsoftware.com \
--cc=git@vger.kernel.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 NNTP newsgroup(s).