On Thursday, Jun 12, 2003, at 04:01 US/Pacific, Eugene Geldenhuys wrote: [..]
I have a small problem after upgrading a system from RH6.0 to RH9.0, my[..]
apache web server went from version 1.3.6 to version 2.0.40. This in itself
is probably a good thing, but a system management utility I wrote in perl
now will not execute system binaries unless I mark them srwxr-xr-x.
p0: did you do a 'cold upgrade' without bit twiddling either the perl or the apache code?
p1: when you su to root and do
suexec -V
does the
-D AP_DOC_ROOT="/var/www"
value point to where you have your DOCUMENT_ROOT rigged to work, normally the default value in the httpd.conf is something like
DocumentRoot "/var/www/html"
hence you should be able to hang any of your stuff that needs to be suexec'd in that path.... I have my Virtual Hosts off say in
/var/www/<virtualHostNameHere>
p2: you do understand that you will need the command
SuexecUserGroup <user> <group>
in your 'virtual host' directives.... vice the older apache 1.3.x versions where it was
User <uname>
Group <group>p3: the executable - perl code - is actually owned by the user/group that will be executing it?
p4: we basically agree that you should NOT need to have the setuid bit set on the executable...
p5: have you any interesting information from the suexec.log that can help you sort out what it is whining about?
ciao drieux
---
-- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
