suexec: disabled?

[Bakki Kudva <ba...@ncinter.net>]

I recently upgraded to perl5.6 and added php4 to my apache server. I
don't know what I did wrong but I am getting the following errors.
If I do a httpd -l I get...

suexec: disabled; invalid wrapper /usr/local/apache/bin/suexec

Also I cannot browse anything in htdocs becuase I get a "You don't have
permission to access / on this server." and the error log contains..

192.168.0.252 - - [31/Aug/2000:17:13:35 -0400] "GET / HTTP/1.0" 403 279

Where do I start to look for this permissions problem? The htdocs looks
is owned by 'nobody'.

An unrelated msg I get when I start the httpd ..
 DBI.pm: defined(@array) is deprecated at
/usr/lib/perl5/site_perl/5.6.0/Apache/DBI.pm line 135.
[Thu Aug 31 17:12:53 2000] DBI.pm:      (Maybe you should just omit the
defined()?)                                                                              

I have installed ApacheDBI version 0.87.

I would appreciate any pointers.

bakki
-- 
      _ _
 .-. |M|S|		Bakki Kudva
 |D|_|a|y|		Navaco
 |o|m|n|s|<\		420 Pasadena Drive
 |c|e|a|t| \\		Erie, PA 16505-1037
 |u|n|g|e|  \\ 		http://www.navaco.com/
 | |T|e|m|   \> 	ph: 814-833-2592
""""""""""""""""""	fax:603-947-5747
e-Docs

Re: suexec: disabled?

[Tom Brown <tb...@baremetal.com>]

On Thu, 31 Aug 2000, Bakki Kudva wrote:

> I recently upgraded to perl5.6 and added php4 to my apache server. I
> don't know what I did wrong but I am getting the following errors.
> If I do a httpd -l I get...
> 
> suexec: disabled; invalid wrapper /usr/local/apache/bin/suexec

your copy of suexec is most likely installed in another location. Either
that or there are some sanity checks that your binary is
failing... in either case, for mod_php and mod_perl it doesn't
matter -- suexec is only for mod_cgi stuff.

> Also I cannot browse anything in htdocs becuase I get a "You don't have
> permission to access / on this server." and the error log contains..
> 
> 192.168.0.252 - - [31/Aug/2000:17:13:35 -0400] "GET / HTTP/1.0" 403 279
> 
> Where do I start to look for this permissions problem? The htdocs looks
> is owned by 'nobody'.

and nobody's home directory is probably more 0700 and the webserver is
running as "httpd" or vice-versa? The _error_ log would show the problem.
You have quoted the access log.