On Mon, Dec 22, 2003 at 04:06:02PM -0800, Stas Bekman wrote:
Use this archive instead:
Thanks for the link.
Hmm, are you sure you've spelled things right? That's t/logs/error_log. Do
you get anything at all written to it?
Yes, I do get some output written to the error_log. It turns out
On Mon, Dec 22, 2003 at 04:02:20PM -0800, Stas Bekman wrote:
By putting it last (after blib):
snip
it ensures that it'll be first in @INC. So it does it right.
Yes, of course, that makes sense. However, when I dump my @INC the blib
directories show up above the project/lib directory:
$VAR1 =
William McKee wrote:
On Mon, Dec 22, 2003 at 04:06:02PM -0800, Stas Bekman wrote:
Use this archive instead:
Thanks for the link.
Hmm, are you sure you've spelled things right? That's t/logs/error_log. Do
you get anything at all written to it?
Yes, I do get some output written
On Tue, Dec 23, 2003 at 10:12:49AM -0500, Geoffrey Young wrote:
this is one danger of using the live-dev thing, you can get confused :) if
you just follow the
$ make t/TEST t/foo.t -v
paradigm you'll always get things right (I use an alias myself :). with
smalish modules it shouldn't
However, I do like the idea of keeping the server
running since it takes several seconds for my slow system to bring it
up. Running `make t/TEST -run-tests` seems to work fine though.
excellent. I don't use that feature myself, so it's good to know it's
working for people :)
--Geoff
William McKee wrote:
On Tue, Dec 23, 2003 at 10:12:49AM -0500, Geoffrey Young wrote:
this is one danger of using the live-dev thing, you can get confused :) if
you just follow the
$ make t/TEST t/foo.t -v
paradigm you'll always get things right (I use an alias myself :). with
smalish modules it
William McKee wrote:
Stas,
A bit more testing has revealed more about modperl_inc.pl to me. I had
neglected to realize that modperl_inc.pl only gets loaded on server
startup. I had been running my tests using the following commands:
t/TEST -start
t/TEST -run-tests
That's the right
William A. Rowe, Jr. wrote:
At 04:47 PM 12/22/2003, Stas Bekman wrote:
I'm not sure this is a good idea to run it on the main host. If it was we
could just as well run post_config for each vhost as well.
No, you missed my earlier point. post_config is a run-once. host_init is
the run-each
[EMAIL PROTECTED] wrote:
+ PR 24469, broken reverse lookups with IPv4-mapped addrs on old OS X
+The autoconf check added between 2.0.47 and 2.0.48 isn't
+sufficient for catching the OS X problem, because building the
+IPv4 numeric address string from IPv4-mapped address would
# apachectl start
(some error message)
Unable to open logs\n
(that \n shouldn't be escaped)
No... the default server is still a server. But you make an interesting point, that
certain percolation occurs in the post config. I suppose I would want that to
happen before my handlers dealt with the per-vhost settings, and I would not
want the changes I make to that global server to
A patch should be easy, but I have no system to test on (upgraded to Panther).
I'm a bit nervous about doing a name lookup at configure time anyway.
I have a 10.1 box that I use as a web server. I have not been upgrading that
machine for several reasons, and can use it for testing stuff out. It
12 matches
Mail list logo
