Message-ID: <00ec01bf66a8$fdd0c640$064b2509@raleigh.ibm.com>
From: "Bill Stoddard" <stoddard@raleigh.ibm.com>
To: <new-httpd@apache.org>
References: <200001220116.UAA25299@devsys.jaguNET.com>
 <059801bf66a3$eb955cc0$0300000a@chl>
Subject: Re: The 1.3.11 release (WIN32)
Date: Mon, 24 Jan 2000 15:24:18 -0500
Organization: IBM Corp.
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Sender: new-httpd-owner@apache.org
Precedence: bulk
Reply-To: new-httpd@apache.org

I think you are using a patched version of Apache, because from what I can
tell we've never passed ap_server_root on the command line in
create_process. This does look like a bug though. I'll take a look at it.

Bill

----- Original Message -----
From: Dovid Zirkind <dovid@tig.com.au>
To: <new-httpd@apache.org>
Sent: Monday, January 24, 2000 2:47 PM
Subject: Re: The 1.3.11 release (WIN32)


>
> B"H
>
> hi,
>
> does anyone know *why* in create_process() the line:
>
>     pCommand = ap_psprintf(p, "\"%s\" -Z %s -d \"%s\" -f \"%s\"", buf,
> exit_event_name, ap_server_root, ap_server_confname);
>
> was changed to:
>
>     pCommand = ap_psprintf(p, "\"%s\" -Z %s -f \"%s\"", buf,
> exit_event_name, ap_server_confname);
>
>
> as now, the following problem occurs:
>
> In windows if the server was started from a drive other than the drive
that
> contains the "ap_server_root" (and possibly also from just another
> directory), and rely on the registry key "ServerRoot" pointing to the
> appropriate directory, the children that are spawned end up dying with an
> error "file not found" because of wrong path.
>
> Bring Moshiach closer by doing acts of kindness!
>
>