perl-modperl mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Faisal Nasim <whiz...@nasim.org>
Subject Re: END block weird behavior
Date Thu, 02 Dec 2004 07:53:01 GMT
At 05:48 AM 12/2/2004, Stas Bekman wrote:
>Faisal Nasim wrote:
>>Okay here's a demonstration:
>>The test script is:
>>#!/usr/local/bin/perl
>>use strict;
>>use vars qw ($mydata);
>>$mydata = 'woodooeer';
>>my $data = 'woodoo';
>>my $data2 = 'dingdong';
>>print "Content-type: text/plain\n\n";
>>print scalar localtime () , "\n\n";
>>print `cat /tmp/modperltest.txt`;
>>END
>>{
>>        open FILE , '>/tmp/modperltest.txt';
>>        print FILE "DATA: " , scalar localtime , "\n";
>>        print FILE "$data\n";
>>        print FILE "$mydata\n";
>>        print FILE "$data2\n";
>>        close FILE;
>>}
>>
>>You can see the different behaviors at:
>>no modperl: http://www.nasim.org/test/short.cgi
>>modperl: http://www.nasim.org/test/short.pl
>>Note that the file is printed first and then updated. Hit refresh
>>to see that modperl misses $mydata.
>
>Actually it's very inconsistent. If I hit reload I get the value of $mydata appearing
and disappearing in both scripts.
>
>Any chance you could rewrite your code not to use the END block for the desired functionality?
At least until we get some freed resources to work on modperl1 issues again?

It is not inconsistent. Note that the file is printed first before its rewritten.
So, when you load the mod_cgi page after mod_perl, you'll still see
a missing element. Hit refresh and you can see it worked great. Not
using END block solved all the problems but if I press STOP while
a processing is being done (takes 2-3 secs), it doesn't call the cleanup
routine and that sometimes leaves the file locks open. I was hoping I
could always perform final cleanup in my END block. I can take a crack
at the source, I've done Apache hacking before.

Regards,

Faisal 
Mime
View raw message