OK, the end of the httpd.conf now reads:


<Perl>
         use Carp ();
         $SIG{__WARN__} = \&Carp::cluck;
         use lib qw(/home1/d/d2ia1/lib/perl5);

</Perl>

PerlModule AxKit
SetHandler axkit
AxAddStyleMap application/x-xpathscript Apache::AxKit::Language::XPathScript
AxLogDeclines On

AxAddStyleMap text/xsl Apache::AxKit::Language::LibXSLT
AxDebugLevel 10



Elsewhere in the file, I've set the following:

LogLevel debug



Still no response, no transforms. The error log says:

[Thu Aug 15 22:29:33 2002] [info] created shared memory segment #1572866
[Thu Aug 15 22:29:33 2002] [notice] Apache/1.3.24 (Unix) AxKit/1.6 
mod_perl/1.26 configured -- res
uming normal operations
[Thu Aug 15 22:29:33 2002] [info] Server built: May 24 2002 22:12:12
[Thu Aug 15 22:29:33 2002] [notice] Accept mutex: sysvsem (Default: sysvsem)

... and the access log shows the server is indeed serving the requests.

The result is the same, whether I tell it to use Sablotron or LibXML, as 
well as when I use the PI in the file (the simple dromedaries test) to set 
an x-pathscript instead of an XSLT stylesheet.

At 02:48 AM 8/15/02, Matt Sergeant wrote:
>On Wed, 14 Aug 2002, [EMAIL PROTECTED] wrote:
>
> > Anyway, since a new AxKit was recently released, I installed it, to see
> > if the problems persisted. With 1.6, I get no segfaults, but AxKit
> > won't process any documents. With the following in the httpd.conf
> >
> > <Perl>
> >         use Carp ();
> >         $SIG{__WARN__} = \&Carp::cluck;
> >         use lib qw(/home1/d/d2ia1/lib/perl5);
> >
> > </Perl>
> >
> > PerlModule AxKit
> > SetHandler perl-script
> > PerlHandler AxKit
>
>Can you try SetHandler axkit instead of the two "SetHandler/PerlHandler"
>lines there? Also you may have to up your actual apache server's LogLevel
>to info or debug to get any AxKit output.
>
>--
><!-- Matt -->
><:->Get a smart net</:->


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to