Re: Can't upgrade from mod_perl 1.29 -> mod_perl 1.99

2005-01-24 Thread Randy Kobes
On Mon, 24 Jan 2005, Ixkorr Oxkarr wrote: > I am running Apache 2.0.40. > > The problem is that I am trying to compile some code > that checks to see if mod_perl 1.99 is installed with > the statement "use mod_perl 1.99;". This fails, even > though I have installed the mod_perl 1.99 RPM and I am >

Re: How to call functions in other files?

2005-01-24 Thread Perrin Harkins
Mark McWiggins wrote: [Mon Jan 24 18:51:56 2005] [error] Undefined subroutine &ModPerl::ROOT::ModPerl::Registry::usr_local_apache2_htdocs_eTracICR_perl_NewNoticeSubmitPart1_2epl::godone called at /usr/local/apache2/htdocs/eTracICR/perl/NewNoticeSubmitPart1.pl line 16, line 20.\n --- How do I

How to call functions in other files?

2005-01-24 Thread Mark McWiggins
Hi Everybody, I'm trying something like: db.pl: godone() { # do something } --- NewNoticeSubmitPart1.pl: require "db.pl"; godone($q,"SessExpired.html"); -- But I get: [Mon Jan 24 18:51:56 2005] [error] Undefined subroutine &ModPerl::ROOT::ModPerl::Registry::usr_local_apache2_htdocs_eTracICR_per

Re: make test failed on solaris 8

2005-01-24 Thread Stas Bekman
Tulan W. Hu wrote: From: "Stas Bekman" <[EMAIL PROTECTED]> [EMAIL PROTECTED] wrote: -8<-- Start Bug Report 8<-- 1. Problem Description: I have tried the httpd-2.0.49 with mod_perl 1.9913 dev version and the make test ran ok. However, the httpd-2.0.52 with

Re: [DOH!] Apache 2 SEGVs during test run

2005-01-24 Thread Stas Bekman
[don't forget to always reply to the list] Dominique Quatravaux wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Stas Bekman wrote: | what test has caused the segfault? can you do the verbose run of | that test? Well I was able to reproduce that failure mode only twice, but one another run gave

Re: Package building

2005-01-24 Thread Philippe M. Chiasson
Paul Armstrong wrote: I'm trying to build packages for mod_perl on Solaris and the usual make DESTDIR=/tmp/mod_perl install doesn't work any more. Apache is in /usr/local but I want mod_perl to install temporarily in /tmp/mod_perl so I can package it before installing into /usr/local with Apache (I

Re: [mp2] Also problems with reloading modules after upgrade

2005-01-24 Thread Philippe M. Chiasson
I hope this can help to locate the problem. Regards, Thomas den Braber -Oorspronkelijk bericht- Van: Thomas den Braber [mailto:[EMAIL PROTECTED] Verzonden: maandag 24 januari 2005 10:47 Aan: 'Thomas den Braber'; modperl@perl.apache.org Onderwerp: RE: [mp2] Also problems with reloading modul

Re: Can't upgrade from mod_perl 1.29 -> mod_perl 1.99

2005-01-24 Thread INFOQUEST USA INC
It's hard to tell without knowing more details. I think that either you upgraded your Apache from 1.3x to 2.x or installed another Apache Server 2.x. I assume that you had installed mod_perl 1.29 with Apache 1.3x and then upgraded to Apache 2.x & mod_perl 1.99. Because mod_perl 1.29 can not be

Re: [mp2] reliable methods to prevent handlers from repeating

2005-01-24 Thread Dorian Taylor
here's my solution to handler loop prevention when the initial request to a handler isn't necessarily the main request: sub handler { my $r = shift; my $mr = $r->main || $r; if ($mr->notes->get(__PACKAGE__ . '::SEEN')) { $r->log->debug("We are looping."); return Apache

Apache Reload -- Subroutine xx redefined

2005-01-24 Thread David Romero
Hi all. i have a problem with apache reload module, when im restart apache all works fine, but on frist change on my module apache reload return an error this is my error [Mon Jan 24 13:00:36 2005] [error] [client 127.0.0.1] Subroutine display redefined at /usr/local/unicon io/Unicornio/Politica/

Re: Can't upgrade from mod_perl 1.29 -> mod_perl 1.99

2005-01-24 Thread Ixkorr Oxkarr
I am running Apache 2.0.40. The problem is that I am trying to compile some code that checks to see if mod_perl 1.99 is installed with the statement "use mod_perl 1.99;". This fails, even though I have installed the mod_perl 1.99 RPM and I am running a version of Apache 2. Clearly, Perl thinks I

Re: Can't upgrade from mod_perl 1.29 -> mod_perl 1.99

2005-01-24 Thread Perrin Harkins
On Mon, 2005-01-24 at 08:04 -0800, Ixkorr Oxkarr wrote: > Is there any way I can force an unload of > mod_perl-1.29? There is no official way of removing perl modules, but you can go in and delete mod_perl.pm and the stuff under Apache/ in your @INC path. - Perrin

Re: Can't upgrade from mod_perl 1.29 -> mod_perl 1.99

2005-01-24 Thread INFOQUEST USA INC
mod_perl 1.99 or later requires Apache 2.0 or later - it doesn't work with Apache 1.3x.   Thanks & Regards     Khalid     - Original Message - From: "Ixkorr Oxkarr" <[EMAIL PROTECTED]> To: Sent: Sunday, January 23, 2005 8:06 PM Subject: Can't upgrade from mo

Re: Can't upgrade from mod_perl 1.29 -> mod_perl 1.99

2005-01-24 Thread Ixkorr Oxkarr
Randy, Thanks for your help. perl -MApache2 -Mmod_perl -e 'print $mod_perl::VERSION' still reports mod_perl-1.29, even after I have done a "make uninstall" in the mod_perl-1.29 source directory, and I have installed the mod_perl-1.99 RPM. Is there any way I can force an unload of mod_perl-1.29?

Re: make test failed on solaris 8

2005-01-24 Thread Tulan W. Hu
>From: "Stas Bekman" <[EMAIL PROTECTED]> >> [EMAIL PROTECTED] wrote: > > -8<-- Start Bug Report 8<-- > > 1. Problem Description: > > > > I have tried the httpd-2.0.49 with mod_perl 1.9913 dev version and > > the make test ran ok. However, the httpd-2.0.5

RE: [mp2] Also problems with reloading modules after upgrade

2005-01-24 Thread Thomas den Braber
Sorry, something was missing: Log from 199_16: Apache::Reload: Checking mtime of Menu2.pm Subroutine Main redefined at /srv/sitegen2/lib/Menu2.pm line 33. Subroutine menuJavaScript redefined at /srv/sitegen2/lib/Menu2.pm line 238. Subroutine reread_conf redefined at /srv/sitegen2/lib/Menu2.pm lin

RE: [mp2] Also problems with reloading modules after upgrade

2005-01-24 Thread Thomas den Braber
Finally I have some more info on this issue. I installed my modperl handler in a virtual host directive and now I see the Apache::Reload debug messages. I found out that there is a difference between reloading in 199_16 and the version above 199_16: I changed the menu2.pm file. Log from 199_16: