httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dean Gaudet <dgau...@arctic.org>
Subject Re: [PATCH] OPTIMIZE_TIMEOUTS doesn't set child usage timestamp
Date Sat, 13 Dec 1997 19:51:18 GMT
It was doing it the OPTIMIZE_TIMEOUTS way up until 1.3b4-dev, one of the
first patches I put in was the one which added child_timeouts.  i.e. 
child_timeouts has never been released.  We still need a 1.3b4 though...
my "stability" statement was just something I posted hoping to get reports
of the contrary :)

Dean

On Sat, 13 Dec 1997, Jim Jagielski wrote:

> Yep... this is better. Course, this definately means we need
> a 1.3b4, since this changes the way Apache is handling
> timeouts since up to now, it's been doing it the "old
> way" if OPTIMIZE_TIMEOUTS has been defined. The below
> makes it do what you originally wanted, but we need to test
> this now.
> 
> +1
> 
> Dean Gaudet wrote:
> > 
> > Oh god.  I goofed.  Your patch isn't needed.  The bug is the value of
> > child_timeouts.  Try this patch instead. 
> > 
> > Dean
> > 
> > Index: http_main.c
> > ===================================================================
> > RCS file: /export/home/cvs/apachen/src/main/http_main.c,v
> > retrieving revision 1.256
> > diff -u -r1.256 http_main.c
> > --- http_main.c	1997/12/12 08:09:19	1.256
> > +++ http_main.c	1997/12/13 08:00:35
> > @@ -3557,7 +3557,7 @@
> >      suexec_enabled = init_suexec();
> >      server_conf = read_config(pconf, ptrans, server_confname);
> >  
> > -    child_timeouts = standalone || one_process;
> > +    child_timeouts = !standalone || one_process;
> >  
> >      if (standalone) {
> >  	open_logs(server_conf, pconf);
> > 
> > 
> 
> 
> -- 
> ====================================================================
>       Jim Jagielski            |       jaguNET Access Services
>      jim@jaguNET.com           |       http://www.jaguNET.com/
>             "Look at me! I'm wearing a cardboard belt!"
> 


Mime
View raw message