Message-Id: <l03110700b176935f4171@[24.128.120.156]>
In-Reply-To: 
 <Pine.LNX.3.96dg4.980506140235.1477E-100000@twinlark.arctic.org>
References: <199805062034.QAA10045@siam.gensym>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Wed, 6 May 1998 18:43:46 -0400
To: new-httpd@apache.org
From: Ben Hyde <bhyde@pobox.com>
Subject: Re: chdir isn't thead specific
Sender: new-httpd-owner@apache.org
Precedence: bulk
Reply-To: new-httpd@apache.org

Dean wrote
>On Wed, 6 May 1998, Ben Hyde wrote:

>> Second, what to do...
>> 
>> A mutex that owns the current working directory looks necessary.
>> 
>> Revising all the subprocess command execution to take a
>> directory would also be good.

Pesky amount of change this late in the game.

>Right, if it took a directory then on unix the chdir() could happen after
>the fork() and everything is all real simple.  On NT... allow me to puke
>again.

brainwashing proceeds more smoothly on an empty stomach

>The CGI "spec" doesn't *require* the current directory to be changed in
>this arcane manner.

Well that's water under the bridge.  The spec is probably out of
synch with practical reality at this point.

I wonder where the chdir to "/" done in the service_cd() falls on
the spectrum from "seemed like a good idea" to "world ends without it"?
If it's on the right then these other chdirs need to switch back
and we can't cache the last one usefully.

spawn_mutex is probably relevant.

  - ben hyde