From: Jim Jagielski <jim@jaguNET.com>
Message-Id: <199712131330.IAA23337@devsys.jaguNET.com>
Subject: Re: [PATCH] OPTIMIZE_TIMEOUTS doesn't set child usage timestamp
To: new-httpd@apache.org
Date: Sat, 13 Dec 1997 08:30:27 -0500 (EST)
In-Reply-To: <Pine.LNX.3.95dg3.971213000430.29165E-100000@twinlark.arctic.org>
 from "Dean Gaudet" at Dec 13, 97 00:11:32 am
Content-Type: text
Sender: new-httpd-owner@apache.org
Precedence: bulk
Reply-To: new-httpd@apache.org

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!"