Thanks for the reply. Unfortunately I need the END block to run for every request. I just was wondering why it altered the way error messages were logged.
Thanks. -----Original Message----- From: Jim Schueler [mailto:jschueler@;tqis.com] Sent: Tuesday, November 12, 2002 2:41 PM To: [EMAIL 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.org/authors/id/T/TQ/TQISJIM/ChildExit_0-1.tar.gz -Jim > 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 an included file that I'm 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 > log file. It is almost as if the END{ } is overwriting the > ModPerlRegistry error system. > > > > Any ideas? > > > > Thanks.
