Well my problem is apparently gone, tho i don't understand it. It seems to have been
caused by preloading modules, using the following in my httpd.conf:
PerlFreshRestart On
PerlModule Apache::DBI
PerlModule AxKit
PerlModule CGI
The debugging process was foiled when i continued to use 'apachectl restart' despite
the PerlFreshRestart (which reloades modules even after they're gone from the conf
file, i guess).
i can't reproduce the problem, but when i reintroduce 'PerlModule XML::Sablotron' i
get the following error. SO i guess that one is better left out of the apache conf!
thanks,d
[Sat Jan 20 14:21:43 2001] [notice] caught SIGTERM, shutting down
Constant subroutine XHTML_DTD redefined at /usr/lib/perl5/5.00503/constant.pm line 175.
Syntax error on line 232 of /etc/httpd/conf/httpd.conf:
Not enough arguments for XML::Sablotron::ProcessStrings at
/usr/lib/perl5/site_perl/5.005/i386-linux/XML/Sablotron.pm line 75, near "@_)"
Not enough arguments for XML::Sablotron::Process at
/usr/lib/perl5/site_perl/5.005/i386-linux/XML/Sablotron.pm line 79, near "@_)"
BEGIN not safe after errors--compilation aborted at
/usr/lib/perl5/site_perl/5.005/i386-linux/XML/Sablotron.pm line 198.
>
>[Cc'd to axkit-users, where the problem came up]
>
>At 01:46 20/01/2001 +0000, Matt Sergeant wrote:
>>The 1; in XML::Sablotron.pm is not right at the end.
>
>Yes, that should definitely be fixed. It does not create a problem because
>it is still the last value returned by use, but it makes it easy to break.
>
>>There's a bigger problem (that may or may not be related) in that with
>>AxKit/mod_perl, for some reason if XML::Sablotron is loaded in the parent
>>httpd processes (before the fork), then when you do XML::Sablotron->new()
>>you get:
>>
>>Can't locate auto/XML/Sablotron/new.al in @INC ...
>
>A stab in the dark but this could be due to a stale copy of Sablotron.pm
>somewhere. Iirc it used AutoLoader before but doesn't anymore. A mix of an
>old Sablotron.pm with a new install could cause conflicts there. MakeMaker
>could be smart enough to remove old .al files if they exist and the new
>version doesn't want them. How that stale copy would get in the way I don't
>know but it only need be earlier in @INC. I'm not experiencing this problem
>with 0.50.
>
>-- robin b.
>Oops. My Brain just hit a bad sector.
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
