G'day Michael,
On 19/09/06, Michael Lake <[EMAIL PROTECTED]> wrote:
Hi
I got my apache working via a cludge. I moved the mod_jk.so in
/usr/lib/apache/1.3/
to one level up :-) Hence apache ain't looking for it no more.
I also did a "apache-modconf apache-perl disable mod_sk"
which didn't complain. apache then started OK.
Now what should I do?
Sorry can't help much.
I had to set up mod_jk and mod_jk2 on apache2 last year (the latter is
deprecated). From your post I can't tell how much you know about it.
Basically we used it to connect to tomcat, so that on certain url's
apache would pass thru the request.
If you are also running Tomcat there in the background, you might have
broken something or someone's java project (or at least the connection
to it).
I didn't know there was any connection with perl although it looks
like you are using perl to configure apache (?) which I can't help you
with.
Can't help on the .info thing.
For mod_jk setup, I had a LoadModule directive which pointed to the
mod_jk.so file, and then several other things besides including links
to tomcat connector files:
LoadModule jk_module
/usr/local/tomcat5.0-connector/native/apache-2.0/mod_jk.so
# Declare the module for <IfModule directive> (remove this line on
Apache 2.0.x)
#AddModule mod_jk.c
# Where to find workers.properties
JkWorkersFile /usr/local/tomcat5.0-connector/conf/workers.properties
... etc ...
(this was a non-debian apache setup)
Rgds
Daniel.
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
