On Sat, 21 Apr 2001, Steve Leibel wrote:
I believe the way this works is that the first time any Apache child
process sees "use Foo" that is the version of Foo.pm that will be
used by that process. No subsequent "use Foo" within components will
have any effect during the life of that Apache
7675 E0FA 561B
- Original Message -
From: "Steve Leibel" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, April 22, 2001 4:14 AM
Subject: Must restart Apache when any .pm changes?
I'm experimenting with using Perl modules (.pm files) underneath
Mason components.
A
I'm experimenting with using Perl modules (.pm files) underneath
Mason components.
As far as I can see, the only way to guarantee that changes made in
the .pm are seen by the Mason code is to restart Apache whever the
.pm file changes. This is true whether the "use" statement is in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At 5:36 AM +0200 4/22/01, Issac Goldstand wrote:
man Apache::StatINC
Issac
Apache::Reload seems better. But if you have "use lib" statements in
your code you'll need some patches to it that I don't believe have
been released yet.
- --
Kee
On Sun, 22 Apr 2001, Kee Hinckley wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At 5:36 AM +0200 4/22/01, Issac Goldstand wrote:
man Apache::StatINC
Issac
Apache::Reload seems better. But if you have "use lib" statements in
your code you'll need some patches to it that I
