You are viewing a plain text version of this content. The canonical link for it is here.
Posted to modperl@perl.apache.org by Steve Leibel <st...@bluetuna.com> on 2001/04/22 04:14:26 UTC
Must restart Apache when any .pm changes?
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
handler.pl or in the component.
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 process.
Am I understanding this correctly?
Re: Must restart Apache when any .pm changes?
Posted by Matt Sergeant <ma...@sergeant.org>.
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 don't believe have
> been released yet.
Actually that's a good prod - I'll try and put out a new release this
weekend.
--
<Matt/>
/|| ** Founder and CTO ** ** http://axkit.com/ **
//|| ** AxKit.com Ltd ** ** XML Application Serving **
// || ** http://axkit.org ** ** XSLT, XPathScript, XSP **
// \\| // ** mod_perl news and resources: http://take23.org **
\\//
//\\
// \\
Re: Must restart Apache when any .pm changes?
Posted by Kee Hinckley <na...@somewhere.com>.
-----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 Hinckley - Somewhere.Com, LLC
http://consulting.somewhere.com/consultants.html#kee
I'm not sure which upsets me more: that people are so unwilling to accept
responsibility for their own actions, or that they are so eager to regulate
everyone else's.
-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 7.0.3 for non-commercial use <http://www.pgp.com>
iQA/AwUBOuL/CyZsPfdw+r2CEQL6OACfeNOrBhEepJYa5gXlxEKBkr6fK7QAn26P
QJDqxJUeiv6lxAEhF4epMjtp
=Q3Cf
-----END PGP SIGNATURE-----
Re: Must restart Apache when any .pm changes?
Posted by Issac Goldstand <ne...@writeme.com>.
man Apache::StatINC
Issac
Internet is a wonderful mechanism for making a fool of
yourself in front of a very large audience.
--Anonymous
Moving the mouse won't get you into trouble... Clicking it might.
--Anonymous
PGP Key 0xE0FA561B - Fingerprint:
7E18 C018 D623 A57B 7F37 D902 8C84 7675 E0FA 561B
----- Original Message -----
From: "Steve Leibel" <st...@bluetuna.com>
To: <mo...@apache.org>
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.
>
> 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
> handler.pl or in the component.
>
> 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 process.
>
> Am I understanding this correctly?
>
Re: Must restart Apache when any .pm changes?
Posted by Dave Rolsky <au...@urth.org>.
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 process.
>
> Am I understanding this correctly?
Yes, mostly. Check out the Apache::Reload module though. It does what I
think you want.
-dave
/*==================
www.urth.org
We await the New Sun
==================*/