*BSD News Article 82072


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.mel.connect.com.au!news.syd.connect.com.au!news.bri.connect.com.au!fjholden.OntheNet.com.au!news
From: Tony Griffiths <tonyg@OntheNet.com.au>
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: execve() failed - damn!!!
Date: Sat, 02 Nov 1996 13:21:59 +1000
Organization: On the Net (ISP on the Gold Coast, Australia)
Lines: 36
Message-ID: <327ABE57.27F@OntheNet.com.au>
References: <3273EF85.1AA9@emil.fberg.molndal.se>
Reply-To: tonyg@OntheNet.com.au
NNTP-Posting-Host: swanee.nt.com.au
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 3.0 (WinNT; I)
To: so@emil.fberg.molndal.se

Paul wrote:
> 
> I'm fairly new at these script-things...and therefore I hope that
> someone can help me. =)
> 
> The "execve() failed" error has been tormenting me for a few weeks
> now. I've downloaded a few perl-scripts that I've seen working on
> other servers. I also have other perl-scripts running on our server
> that don't give me this error. These new ones do though.
> The path at the top of the script IS the right one (the same as for my
> other perl-scripts that DO work). I can ALSO execute the script
> successfully from the command line (perl scriptname.cgi) AND I have
> chmoded everything to 644, 777, 756 and so on - I've tried most
> combinations.

You havn't, by any chance, put some "rubbish" on the first line of the
perl script after the "#!/.../perl"?  I saw a similar problem where
someone put a comment (beginning with a #) on this line and it generated
the execve() failure just like you are experiencing!

One we removed the comment, we still got the error UNTIL we remove ALL
white space at the end of this line!!!  Apparently, the code simply
tries to execve() everything after the first 2 characters to the
<End-of-Line> including white space.  Of course the filesystem cannot
find such a file and so the error!

> I have also searched the web for explanations for this error but every
> FAQ says that it's the path to the perl-handler.
> 
> Could the origin of this error possibly be more than this path-thing?
> Thanks in advance...
> 
> /Paul

Regards,
Tony