Re: Testers; Apache 2.0 release candidate is tagged

[André Schild]

William A. Rowe, Jr. schrieb:

At 02:20 PM 3/25/2003, André Schild wrote:
 

William A. Rowe, Jr. schrieb:

   

Apache 2.0 testers,

can you please help move forward the next HTTPD release by
checking out httpd-2.0 from the WROWE_2_0_45_RC1 tag?
 

The SSLMutex always creates this message in the error log on the first access
with a HTTPS request:
[Tue Mar 25 21:04:55 2003] [warn] (OS 123)Die Syntax für den Dateinamen, Verzeichnisnamen oder die Datenträgerbezeichnung ist falsch.  : Cannot reinit SSLMutex
   

I got the message from it's number (thank goodness we finally group
these by 'role') - and I'm diagnosing now.
 

There is a small error in my previous mail.
Of course I use the
SSLMutex default

config entry, as on win32 you only have the choice between none and default.

I'm using openssl 0.9.7a and MS dev studio 6.0

André

Re: Testers; Apache 2.0 release candidate is tagged

[William A. Rowe, Jr.]

At 02:20 PM 3/25/2003, André Schild wrote:
>William A. Rowe, Jr. schrieb:
>
>>Apache 2.0 testers,
>>
>> can you please help move forward the next HTTPD release by
>>checking out httpd-2.0 from the WROWE_2_0_45_RC1 tag?
>
>The SSLMutex always creates this message in the error log on the first access
>with a HTTPS request:
>
>[Tue Mar 25 21:04:55 2003] [warn] (OS 123)Die Syntax für den Dateinamen, 
>Verzeichnisnamen oder die Datenträgerbezeichnung ist falsch.  : Cannot reinit SSLMutex

I got the message from it's number (thank goodness we finally group
these by 'role') - and I'm diagnosing now.

Bill 

Re: Testers; Apache 2.0 release candidate is tagged

[André Schild]

William A. Rowe, Jr. schrieb:

Apache 2.0 testers,

 can you please help move forward the next HTTPD release by
checking out httpd-2.0 from the WROWE_2_0_45_RC1 tag?  This
should look something like;
 

Hello I did the RC1 build for win32.
So far it looks good, rotatelogs/pipe logs seems to work again.
But one thing with SSL causes me troubles.
The SSLMutex always creates this message in the error log on the first 
access
with a HTTPS request:

[Tue Mar 25 21:04:55 2003] [warn] (OS 123)Die Syntax für den Dateinamen, 
Verzeichnisnamen oder die Datenträgerbezeichnung ist falsch.  : Cannot 
reinit SSLMutex

Sorry, I have a german OS, but the meaning of the message is:

Syntax for the filename, directoryname or volumename is wrong.
I actually have SSLMutex left on the default setting of ssl.conf,
which looks:
#   Semaphore:
#   Configure the path to the mutual exclusion semaphore the
#   SSL engine uses internally for inter-process synchronization.
SSLMutex  file:logs/ssl_mutex
Even trying to specify a full path/filename with / and \ didn't help
to resolve this message.
According to the changes.txt there where modifications
in the SSLMutex stuff in the 2.0.45 changes.
Any ideas ?

André

Re: Testers; Apache 2.0 release candidate is tagged

[Greg Ames]

Greg Ames wrote:

  can you please help move forward the next HTTPD release by
checking out httpd-2.0 from the WROWE_2_0_45_RC1 tag?  
I'm done testing and happy with it on daedalus, with the patch to buildconf of 
course.  I intend to bounce the production server over to this build later 
today, once the load goes down.

Greg

Re: Testers; Apache 2.0 release candidate is tagged

[Jeff Trawick]

William A. Rowe, Jr. wrote:
Apache 2.0 testers,

  can you please help move forward the next HTTPD release by
checking out httpd-2.0 from the WROWE_2_0_45_RC1 tag?  This
should look something like;
WROWE_2_0_45_RC1 looks good for me on Unix (prefork, worker MPMs on 
Linux and AIX)

Re: Testers; Apache 2.0 release candidate is tagged

[André Malo]

* William A. Rowe, Jr. wrote:

> Oh - testing before/after with httpd-test/perl-framework really helps justify
> the patch - especially if you can create a scenario if none exists already.

Since the fixes I want to test only affect non-unices ...
is there a way to let it run under win32? (I don't get it working).

nd
-- 
print "Just Another Perl Hacker";

# André Malo,  #

Re: Testers; Apache 2.0 release candidate is tagged

[Greg Ames]

William A. Rowe, Jr. wrote:
Apache 2.0 testers,

  can you please help move forward the next HTTPD release by
checking out httpd-2.0 from the WROWE_2_0_45_RC1 tag?  
It's running on port 8092 on apache.org if anyone wants to check it out there. 
My initial tests look fine, but I'm too burnt out at the moment to finish some 
of the testing I wanted to do before putting it into production.

Greg

Re: Testers; Apache 2.0 release candidate is tagged

[William A. Rowe, Jr.]

At 04:47 PM 3/24/2003, André Malo wrote:
>* William A. Rowe, Jr. wrote:
>
>> Apache 2.0 testers,
>> 
>>   can you please help move forward the next HTTPD release by
>> checking out httpd-2.0 from the WROWE_2_0_45_RC1 tag?  This
>> should look something like;
>
>Just a question: does it mean, there's no chance to get the outstanding 
>patches of mod_rewrite in?
>
>(I know, we should hurry a bit with that release, but the patches are still 
>waiting for review since exactly one month ...)

Understandable - unfortunately only Brad weighed in, and he forgot to
indicate exactly which of the several rewrite patches he tested.

I'll review tonight and see which I have time to +1 myself.  I would ask
for extra eyeballs before we incorporate any patches at this late date.
Bugs hanging around is bad - but introducing new regressions is worse.

By the way, anyone can suggest that an issue is a SHOWSTOPPER
to the next release, although it better be a showstopper.  I would suggest
you snip those explicit backports that you believe would resolve this bug
to the list, the section in 2.0-dev's STATUS can be hard to follow.

Oh - testing before/after with httpd-test/perl-framework really helps justify
the patch - especially if you can create a scenario if none exists already.

Bill

Re: Testers; Apache 2.0 release candidate is tagged

[André Malo]

* William A. Rowe, Jr. wrote:

> Apache 2.0 testers,
> 
>   can you please help move forward the next HTTPD release by
> checking out httpd-2.0 from the WROWE_2_0_45_RC1 tag?  This
> should look something like;

Just a question: does it mean, there's no chance to get the outstanding 
patches of mod_rewrite in?

(I know, we should hurry a bit with that release, but the patches are still 
waiting for review since exactly one month ...)

nd
-- 
my @japh = (sub{q~Just~},sub{q~Another~},sub{q~Perl~},sub{q~Hacker~});
my $japh = q[sub japh { }]; print join   #
 [ $japh =~ /{(.)}/] -> [0] => map $_ -> ()  #André Malo #
=> @japh;# http://www.perlig.de/ #