On Tue, May 25, 2010 at 5:32 PM, Jonas Bull wrote:
> It isn't always variable related... But I can see where maybe upload
> new version=>refresh page=>get a stale process could be happening.
It shouldn't, since the mtime check on the file happens at the
beginning of handling the request. You mi
It isn't always variable related... But I can see where maybe upload
new version=>refresh page=>get a stale process could be happening.
In this situation the httpd does not recognize the -X option.
I guess we'll have to wait longer.
A server update is in the works, though.
Jonas Bull
601-324-0
On Tue, May 25, 2010 at 4:01 PM, Jonas Bull wrote:
> In the logs, I see notification of the changes to the script
> - sometimes. Most of the time, actually. But occasionally the
> process fails to catch the changes, which is annoying, but not as
> troubling as the case where the script seems to
Apologies for the direct reply. Apparently the list isn't its own reply-to...
#Code_has_been_changed__but_it_seems_the_script_is_running_the_old_code
Describes pretty much what is happening, except the code changes in
question are definitively NOT in modules, which is why I find it
strange. In
[ please keep it on the mailing list ]
On Tue, May 25, 2010 at 2:25 PM, Jonas Bull wrote:
> httpd.conf has the following:
> SetHandler perl-script
> PerlSendHeader On
> PerlHandler Apache::Registry
> Options ExecCGI
Okay,
On Tue, May 25, 2010 at 10:22 AM, Jonas Bull wrote:
> During an active development cycle, with many changes and updates,
> perl cgi pages are getting "stuck" in the mod_perl.
How are you running this code? Is it through ModPerl::Registry? Are
there modules involved?
- Perrin
