From owner-freebsd-questions Sun Oct 20 13:21:01 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA12001 for questions-outgoing; Sun, 20 Oct 1996 13:21:01 -0700 (PDT) Received: from gatekeeper.barcode.co.il (gatekeeper.barcode.co.il [192.116.93.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA11990 for ; Sun, 20 Oct 1996 13:20:51 -0700 (PDT) Received: (from nadav@localhost) by gatekeeper.barcode.co.il (8.7.5/8.6.12) id WAA14933; Sun, 20 Oct 1996 22:20:44 +0200 (IST) Date: Sun, 20 Oct 1996 22:20:44 +0200 (IST) From: Nadav Eiron To: questions@freebsd.org Subject: exec won't run interpreted files. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Continuing my Apache saga... I've narrowed down the problem to a failure of exec to run interpreted files. When Apache tries to exec a CGI script, and it's an interpreted file, the shell (presumeably) will give: /usr/local/.../test-cgi: Can't open /usr/local.../test-cgi This also happens if I let Apache run a binary that does a similar exec - the binary will run, but all I get from the script is this error message in the logs (the exec naturaly works perfectly when run from the command line). Are we right in assuming this error is from the shell starting to execute? (the exec seems succssful, as it does not return). What could cause such a behaviour? This is the same for /bin/sh and /usr/bin/perl. TIA Nadav