Hi Nicolas
Of course, one way of fixing this up is ensuring we use a test framework
that cleans everything up.
As it stands, we could potentially have Apache processes left hanging
around...
In fact we could have a service left running that seems to be the
standard Apache service but is in
There's an old thread below about testing on Win32.
As afar as I can recall, Nicolas Lehuen is the only guy who's been able
to run the tests on win32
Has anybody else been able to? Can we put together some hints as to how
to do it?
David
David Fraser wrote:
Nicolas Lehuen wrote:
Being
I'm a bit confused by:
- The only trick is that you'll have to stop your Apache server
before launching
the test, as the start/stop command can only apply to one single
Apache instance.
Does this apply to UNIX as well as Win32?
I ask as I have never bothered to explicitly shut down any
My bad... It seems it's not necessary to stop the Apache server. I was a bit confused by the Apache Monitor, a Win32 application putting an icon in the tray area showing the state of the Apache server and allowing you to control it. Turns out the monitor is a bit messed up by the test procedure,
Hi Nicolas
Interesting, I never even tried running it the same time as the service,
so I can see that actually works now (except for the monitor problem).
Yes, my patch fixes the problem with the monitor
David
Nicolas Lehuen wrote:
Woops, I've marked the issue as resolved since I've
