You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Alexei Kosut <ak...@organic.com> on 1997/09/05 20:18:57 UTC

Status on Windows

As a bug reporter pointed out, Apache on Windows uses short status
reports, with no way to easily change them to long ones - and it gives
you a message about changing Configuration, which is incorrect.

Since the rationale for short/long scoreboards was to save space and time
when writing scoreboards to disk on systems that do that, and since on
Windows, the scoreboard is just a normal chunk of memory allocated by
malloc(), is there any reason we shouldn't just do this? (untested)

Index: conf.h
===================================================================
RCS file: /export/home/cvs/apachen/src/main/conf.h,v
retrieving revision 1.130
diff -u -r1.130 conf.h
--- conf.h	1997/08/28 01:36:59	1.130
+++ conf.h	1997/09/05 18:18:40
@@ -630,6 +630,7 @@
    chdir() */
 #include <direct.h>
 
+#define STATUS
 #define WIN32_LEAN_AND_MEAN
 #define STRICT
 #define NO_UNISTD_H


-- Alexei Kosut <ak...@organic.com>


Re: Status on Windows

Posted by Ben Laurie <be...@algroup.co.uk>.
Alexei Kosut wrote:
> 
> As a bug reporter pointed out, Apache on Windows uses short status
> reports, with no way to easily change them to long ones - and it gives
> you a message about changing Configuration, which is incorrect.
> 
> Since the rationale for short/long scoreboards was to save space and time
> when writing scoreboards to disk on systems that do that, and since on
> Windows, the scoreboard is just a normal chunk of memory allocated by
> malloc(), is there any reason we shouldn't just do this? (untested)

Also bearing in mind that the (well, at least, my) primary aim for a
Win32 port is to allow people to test stuff without having to have
access to a Unix box, efficiency is not the main concern.

In short, +1.

Cheers,

Ben.

-- 
Ben Laurie            |Phone: +44 (181) 994 6435|Apache Group member
Freelance Consultant  |Fax:   +44 (181) 994 6472|http://www.apache.org
and Technical Director|Email: ben@algroup.co.uk |Apache-SSL author
A.L. Digital Ltd,     |http://www.algroup.co.uk/Apache-SSL
London, England.      |"Apache: TDG" http://www.ora.com/catalog/apache

Re: Status on Windows

Posted by Dean Gaudet <dg...@arctic.org>.
-DSTATUS imposes more system time overhead ... in particular it does a
bunch more system calls.  It's a bit better since the virtual-time
(OPTIMIZE_TIMEOUTS) patch went in.  When I'm benchmarking the server I
always disable STATUS.

Dean

On Fri, 5 Sep 1997, Alexei Kosut wrote:

> As a bug reporter pointed out, Apache on Windows uses short status
> reports, with no way to easily change them to long ones - and it gives
> you a message about changing Configuration, which is incorrect.
> 
> Since the rationale for short/long scoreboards was to save space and time
> when writing scoreboards to disk on systems that do that, and since on
> Windows, the scoreboard is just a normal chunk of memory allocated by
> malloc(), is there any reason we shouldn't just do this? (untested)
> 
> Index: conf.h
> ===================================================================
> RCS file: /export/home/cvs/apachen/src/main/conf.h,v
> retrieving revision 1.130
> diff -u -r1.130 conf.h
> --- conf.h	1997/08/28 01:36:59	1.130
> +++ conf.h	1997/09/05 18:18:40
> @@ -630,6 +630,7 @@
>     chdir() */
>  #include <direct.h>
>  
> +#define STATUS
>  #define WIN32_LEAN_AND_MEAN
>  #define STRICT
>  #define NO_UNISTD_H
> 
> 
> -- Alexei Kosut <ak...@organic.com>
> 
>