On Jun 22, 2004, at 3:34 PM, David Wheeler wrote:
I doubt so. Just make it die with the appropriate message, so that if
someone needs it they will know that it'll be added in the future.
Okay, done.
Uh, and here it is.
Regards,
David
Randy Kobes wrote:
On Tue, 22 Jun 2004, David Wheeler wrote:
On Jun 22, 2004, at 7:32 AM, Randy Kobes wrote:
Right now the Makefile is generated by methods within
Apache/TestConfigC.pm, which generally consists of calling
the apxs utility to compile the module (as well as
implementing a 'clean'
I am getting another strange problem.
I compile and install apache 2.0.49 for both fedora core 1 and red-hat
linux.
Everything seems okay, and installs properly.
When I start httpd manually, it start running and when I do wget using
http://localhost It works fine in both the machines.
But, when
On Jun 22, 2004, at 5:15 PM, Stas Bekman wrote:
David Wheeler wrote:
I figured. I like my style, too (mainly just cperl-mode style). ;-)
pretty much the same here, cperl-mode too :)
For HTML::Mason we found it helpful to add the following as the first
line of source files:
# -*-
On Tue, 22 Jun 2004, Abhishek Khandelwal wrote:
I am getting another strange problem.
I compile and install apache 2.0.49 for both fedora core 1 and red-hat
linux.
Everything seems okay, and installs properly.
When I start httpd manually, it start running and when I do wget using
Where exactly I put this?
In the conf file generated by test, which is in t/conf/httpd.conf
or even before compiling and building test, I change the original
httpd.conf?
Also, where exactly do I put this SSLMutex default?
Abhishek
On Tue, 2004-06-22 at 19:47, Randy Kobes wrote:
On Tue, 22
On Tue, 22 Jun 2004, Abhishek Khandelwal wrote:
Where exactly I put this?
In the conf file generated by test, which is in t/conf/httpd.conf
or even before compiling and building test, I change the original
httpd.conf?
Try changing the original first - I think Apache-Test should
pick up
I changed original ssl.conf
to the SSLMutex default as shown below.
# Semaphore:
# Configure the path to the mutual exclusion semaphore the
# SSL engine uses internally for inter-process synchronization.
#SSLMutex file:/opt/oss/var/apache2/run/ssl_mutex
SSLMutex default
Then I
On Tue, 22 Jun 2004, Abhishek Khandelwal wrote:
I changed original ssl.conf
to the SSLMutex default as shown below.
# Semaphore:
# Configure the path to the mutual exclusion semaphore the
# SSL engine uses internally for inter-process synchronization.
#SSLMutex
On Tue, Jun 22, 2004 at 06:08:17PM -0700, Abhishek Khandelwal wrote:
I am getting another strange problem.
I compile and install apache 2.0.49 for both fedora core 1 and red-hat
linux.
Everything seems okay, and installs properly.
When I start httpd manually, it start running and when I do
Ken Williams wrote:
On Jun 22, 2004, at 5:15 PM, Stas Bekman wrote:
David Wheeler wrote:
I figured. I like my style, too (mainly just cperl-mode style). ;-)
pretty much the same here, cperl-mode too :)
For HTML::Mason we found it helpful to add the following as the first
line of source files:
David Wheeler wrote:
Now committed with a few minor tweaks, please test it since I don't know how
to test it. Thanks David.
Moreover, I think it's time to give you commit access to A-T if you
wish to. Do you have an account at apache.org?
I don't. How do I get one? A quick look around
David Wheeler wrote:
On Jun 23, 2004, at 9:02 AM, Stas Bekman wrote:
Now committed with a few minor tweaks, please test it since I don't
know how to test it. Thanks David.
Cool, thanks. What do you need to be able to feel comfortable/ready to
release it?
As I mentioned I don't know how to test
I think you misunderstood the problem.
I did not build single binary. I seperately build binaries on Red-hat
and Fedora machines. i.e I build httpd on two different machine one
running Red-hat and one running Fedora core 1.
Moreover, I am running Red-hat 9
Its some kind of library
hi all.
we have been using Apache-Test to run our entire testing framework, which is
great - we can mix and match apache-related and non-apache related tests
under the same testing tree and it all works without a hitch.
the only problem is that when working on small testing units that don't
hi all...
as suggested by stas in a recent thread, it's about time we gave david
commit access to the perl-framework - he has been actively helping with the
project for as long as I can remember, from mac-specific stuff to lots of
great work on the (often thin) docs. and now he is working
On Wed, 23 Jun 2004, Geoffrey Young wrote:
hi all...
as suggested by stas in a recent thread, it's about time we gave david
commit access to the perl-framework - he has been actively helping with the
project for as long as I can remember, from mac-specific stuff to lots of
great work on the
Stas Bekman wrote:
David Wheeler wrote:
On Jun 23, 2004, at 9:02 AM, Stas Bekman wrote:
Now committed with a few minor tweaks, please test it since I don't
know how to test it. Thanks David.
Cool, thanks. What do you need to be able to feel comfortable/ready to
release it?
As I
Geoffrey Young wrote:
hi all.
we have been using Apache-Test to run our entire testing framework, which is
great - we can mix and match apache-related and non-apache related tests
under the same testing tree and it all works without a hitch.
the only problem is that when working on small testing
+1
:)
+if ($self-{opts}-{'no-httpd'}) {
+warning skipping configuration: -no-httpd specified;
may be it's better to sayskipping httpd configuration?
sure, that's fine.
+return
please don't forget ; if } is on the next line.
oops :)
may be use -nohttpd, so
20 matches
Mail list logo