On Thu, 26 Feb 2004, Stas Bekman wrote:

> Steve Hay wrote:
> > Hi,
> >
> > I've just tried out Apache-Test 1.08 (on Win32) and noticed that when I
> > ran its test suite with Apache 1.3.29 I was left with an Apache.exe
> > process running afterwards.
> >
> > I think I've seen this happen before, but never got round to looking at
> > it.  Having now looked closer at the command-line being used to kick off
> > the server, it seems to be wrong:
> >
> >     C:/apache/apache.exe -d C:/Temp/Apache-Test-1.08/t -f
> > C:/Temp/Apache-Test-1.08/t/conf/httpd.conf -DAPACHE1 -X
> >
> > The problem is that there is no space between the "-D" and the
> > "APACHE1".  That probably causes the "-X" to be ignored, hence two
> > Apache.exe processes get kicked off, and only one gets killed later.
> > (The "-X", of course, was to avoid that situation.)
>
> What's exactly the problem, Steve? You mean Apache 1's parses '-DAPACHE1 -X'
> as -DAPACHE1=-X?
>
> > The attached patch corrects this error (which was repeated in various
> > places!), and fixes my problem with an Apache.exe being left behind.
>
> I don't like that solution, as it's very confusing when
> you are used to -DFoo.  I need to understand first why do
> you get this problem. May be on Win32 it wants
> '-DAPACHE1=' ? Or if this is something special to -X we
> could orrange to make it come first.
>
> > Both Apache1 and Apache2 require the space, btw, so the patch works fine
> > for my Apache 2 setup as well.
>
> Any pointers to that 'require the space' note?

I'm afraid this will just muddy the waters, but I find that,
using Apache/1.3.27 and then Apache/2.0.48 on Win32, that
Apache-Test is OK as is, and does shut down all processes it
created. Having said that, though, at one point in the past
I remember that on Win32 the space after the '-D' was
needed, but now I can't reproduce such a scenario.

Steve, if you start up Apache from the command line with
some -DFoo, does Apache recognize Foo as being defined,
both on Apache/1 and Apache/2? Or is a space needed?

-- 
best regards,
randy

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to