----------------------------------------------------------------
BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
WHEN YOU POST, include all relevant version numbers, log files,
and configuration files. Don't make us guess your problem!!!
----------------------------------------------------------------
Thanx Fernando
You raised an interesting point.. make suexec? I tried it and it complained "no rule
suexec"
I have never told it to use suexec in fact I didn't know it was a config option since
I've
been using the install docs that came with jserv to the letter (about 20 times now)
Actually I have completly erased everything remotely related to apache and jserv a
number of times and I stil have this problem. I just tried a make clean, which in
light
of what I just said should not be necessary but why not give it a try.
Just got the same error :(
Thanx anyway...
Chris
On Thu, 27 Apr 2000 13:51:35 -0400, Fernando Salazar wrote:
>----------------------------------------------------------------
>BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
>WHEN YOU POST, include all relevant version numbers, log files,
>and configuration files. Don't make us guess your problem!!!
>----------------------------------------------------------------
>
>
>
>>
>> Hi I tried Garrison's procedures and it's pretty much as
>> described in the Jserv docs
>> for compiling DSO. Everything went fine.. except running Apache :(
>>
>> Still if I run /usr/local/apache/bin/httpd -l
>>
>> It complains:
>>
>> Compiled-in modules:
>> http_core.c
>> mod_env.c
>> mod_log_config.c
>> mod_mime.c
>> mod_negotiation.c
>> mod_status.c
>> mod_include.c
>> mod_autoindex.c
>> mod_dir.c
>> mod_cgi.c
>> mod_asis.c
>> mod_imap.c
>> mod_actions.c
>> mod_userdir.c
>> mod_alias.c
>> mod_access.c
>> mod_auth.c
>> mod_so.c
>> mod_setenvif.c
>> suexec: disabled; invalid wrapper /usr/local/apache/bin/suexec
>>
>> And I haven't even started to put JServ in yet.. clearly there a
>> fundamental thing here I
>> am missing
>>
>> susexec is there and it has no denial permissions to anyone.. I
>> can even run
>> susexec from my commandline.
>>
>> Any more ideas?
>>
>> Thanx
>>
>
>Here's my guess:
>
>suExec in Apache requires a separate make step to become active. it sounds
>like
>your original Apache configure was done with --enable-suexec, but no
>subsequent make suexec
>was done. Even if you have done a configure not specifying suexec, that
>setup may
>still be active if you haven't done a clean.
>
>Suggestion:
>
>- do make clean on apache
>- re-do the Apache & JServ configure stuff that was sent in an earlier post.
>
>Hope this helps.
>
>- Fernando
>
>
>
>--
>--------------------------------------------------------------
>Please read the FAQ! <http://java.apache.org/faq/>
>To subscribe: [EMAIL PROTECTED]
>To unsubscribe: [EMAIL PROTECTED]
>Archives and Other: <http://java.apache.org/main/mail.html>
>Problems?: [EMAIL PROTECTED]
>
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
