in reply to Re: Apache::StatINC reload explaination required
in thread Apache::StatINC reload explaination required

Is Module2 in your %INC path, or have you modified %INC in Module1 in order that you can load Module2?

Apache::StatINC checks the last modified time of each module in your %INC hash at the initialisation phase. If the module isn't there or hasn't changed it wont be reloaded. If you're loading Module2 from outside your %INC in Module1 you should modify your startup.pl so that directory is included.

Let us know how you get on.

Steve.
  • Comment on Re: Re: Apache::StatINC reload explaination required

Replies are listed 'Best First'.
Re: Re: Re: Apache::StatINC reload explaination required
by rdfield (Priest) on Sep 05, 2002 at 09:37 UTC
    Module2 is in the same directory as Module1. As you can see from the error.log StatINC correctly identifies the module as requiring a reload, but the reload does not take effect until the calling module has been 'touched' and therefore reloaded. I looked at the code for Apache::Reload and as far as I could tell the only relevent difference was that the reload was done directly rather than through an eval. I changed my local StatINC to remove the eval and tried again to no avail.

    rdfield

[reply]

In Section Seekers of Perl Wisdom