Hi, I’m trying to use the END{ } block in my Perl
Scripts to do some code clean up (making sure files are not locked) at the end
of each request. It seems to be working fine. I’m using Apache::Registry
to run a regular Perl script. I’m having a problem with error
messages.
I have a
Hello Justin.
I've done a little work on a similar problem due to Apache::Registry's
unusual treatment of END {} blocks. You may want to take a look at
the module I recently submitted:
http://www.cpan.org/authors/id/T/TQ/TQISJIM/ChildExit_0-1.tar.gz
-Jim
> Hi, I'm trying to use the END{ } blo
PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: RE: Using Perl END{} with Apache::Registry
Hello Justin.
I've done a little work on a similar problem due to Apache::Registry's
unusual treatment of END {} blocks. You may want to take a look at
the module I recently submitted:
http://www.cpan.o
Justin Luster wrote:
I have an included file that Im requiring:
require test.pl;
Without the END { } block if the script cannot find test.pl I get a
Server error 500 and an appropriate error message in the log file. When
I include the END{ } block I get no Server Error and no message in the
day, November 12, 2002 3:34 PM
To: Justin Luster
Cc: [EMAIL PROTECTED]
Subject: Re: Using Perl END{} with Apache::Registry
Justin Luster wrote:
> I have an included file that I'm requiring:
>
> require "test.pl";
>
> Without the END { } block if the script cannot find t
EMAIL PROTECTED]>
To: "'Perrin Harkins'" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, November 12, 2002 3:34 PM
Subject: RE: Using Perl END{} with Apache::Registry
> No. If there is an END block empty or not then the error logging does
> not happe
-
From: Jim Schueler [mailto:jschueler@;tqis.com]
Sent: Tuesday, November 12, 2002 9:02 PM
To: Justin Luster
Subject: RE: Using Perl END{} with Apache::Registry
Pity that the module doesn't help.
I spent many hours testing END {} block behavior in Apache::Registry and
relied heavily on logged
Justin Luster wrote:
After doing some additional testing it appears that this problem only
occurs on my Windows machine with Apache 2.0. I tried it on my Linux
box Apache 1.3 and things worked fine.
That's a key distinction. Please make sure you say mod_perl 2 when
that's what you are using
