Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 31719 invoked by uid 500); 23 Dec 2002 13:51:57 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 31705 invoked from network); 23 Dec 2002 13:51:56 -0000 From: Jim Jagielski Message-Id: <200212231351.IAA19209@devsys.jaguNET.com> Subject: Re: CGI hosed in v2.0.43 To: dev@httpd.apache.org Date: Mon, 23 Dec 2002 08:51:52 -0500 (EST) Reply-To: jim@jaguNET.com In-Reply-To: from "Graham Leggett" at Dec 23, 2002 01:44:13 PM X-Mailer: ELM [version 2.5 PL5] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Graham Leggett wrote: > > Hi all, > > We have a CGI script that uses cvs to update a source code tree, then > uses ant to build the tree. This script worked 100% under Apache > v1.3.27, but it no longer works in v2.0.43 (or the Redhat v8.0 supplied > v2.0.40) > > The script gets as far as running cvs, which does part of what it needs > to do, and then hangs solid. No errors of any kind are logged in the > error log. The request eventually times out completely. > > So... my question is: What has changed with regards to CGI between v1.3 > and v2.0? Are there extra settings that need to be set? Is the RAM > restricted in some way, is there any reason why cvs should work from the > command line but not from the CGI script? > Is it possible to see the script, or at least a flow of what the script does? Hmmm... could it possibly be an envar issue? -- =========================================================================== Jim Jagielski [|] jim@jaguNET.com [|] http://www.jaguNET.com/ "A society that will trade a little liberty for a little order will lose both and deserve neither" - T.Jefferson