On Tue, 2003-08-05 at 04:55, [EMAIL PROTECTED] wrote:
> loads the module but doesn't import the symbols since it is equivalent to
> the use Foo::Bar (). Therefore I should use "use Foo::Bar" in each program
> only to make the import.
Correct.
> Is there other way to load the module and import the
Hello [EMAIL PROTECTED],
Tuesday, August 05, 2003, 2:55:52 PM, you wrote:
cfr> Hi list,
cfr> One questions for the braves ;-)
cfr> As I understand, the directive
cfr> PerlModule Foo::Bar
cfr> loads the module but doesn't import the symbols since it is equivalent to
cfr> the use Foo::Bar (). T
Mike P. Mikhailov wrote:
Hello [EMAIL PROTECTED],
Tuesday, August 05, 2003, 2:55:52 PM, you wrote:
cfr> Hi list,
cfr> One questions for the braves ;-)
cfr> As I understand, the directive
cfr> PerlModule Foo::Bar
cfr> loads the module but doesn't import the symbols since it is equivalent to
cf
August 05, 2003 7:08 PM
> To: Mike P. Mikhailov
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: PerlModule options?
>
>
> Mike P. Mikhailov wrote:
> > Hello [EMAIL PROTECTED],
> >
> > Tuesday, August 05, 2003, 2:55:52 PM, you wrote:
> >
> > c
Sent: Tuesday, August 05, 2003 2:23 PM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Re: PerlModule options?
>
>
> Hello [EMAIL PROTECTED],
>
> Tuesday, August 05, 2003, 2:55:52 PM, you wrote:
>
> cfr> Hi list,
>
> cfr> One questions for the br
On Tue, 2003-08-05 at 15:57, [EMAIL PROTECTED] wrote:
> Thanks for your answer, this should do it indeed. Super! Somehow I didn't
> think about perl sections...
Perl sections will not work for this. If you do it there, the symbols
you want will only get imported into the Apache::ReadConfig namesp
[EMAIL PROTECTED] wrote:
Hi again Stas & Perrin,
So, its a no-can-do then.
I'll keep putting the "use" in every module to import the symbols in the
proper namespace.
Alternatively I guess I could probably use the functions with fully qualfied
name Apache::ReadConfig::myFunction(), however this wo
gramEz.net
> -Original Message-
> From: Perrin Harkins [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, August 05, 2003 8:29 PM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Re: PerlModule options?
>
>
> On Tue, 2003-08-05 at 04:55, [EMAIL PROTECTED] wrote:
&g
At 7:04 PM +0800 3/23/02, Stas Bekman wrote:
>If all you want to do is to be able to load the module only during
>the restart use in startup.pl:
>
> if ($Apache::Server::ReStarting) {
> require "My::Sensitive::Module";
> }
No, the module has to be loaded during both phases, other wise
Kee Hinckley wrote:
> At 4:18 PM -0500 3/22/02, Perrin Harkins wrote:
>
>> Modules loaded with PerlModule and PerlRequire are not supposed to be
>> loaded again the second time. I seem to remember that they are loaded
>> again when using DSO though, so if you're using DSO you may want to
>> r
At 5:11 PM -0500 3/22/02, Perrin Harkins wrote:
>In your case, PerlFreshRestart might help with what you're trying to
>do since it will clear %INC, but you may still have the problem with
>needing to call Init.
PerlFreshRestart will reload the module and thus call Init, but
PerlFreshRestart is
At 5:11 PM -0500 3/22/02, Perrin Harkins wrote:
>Kee Hinckley wrote:
>>At Embperl 2.0b6 Gerald switched to a new architecture. The
>>previous version was just a plain Perl module loaded as a handler
>>by mod_perl. This version is also an Apache module.
>
>Okay, if it's only in the recent betas
Kee Hinckley wrote:
> At Embperl 2.0b6 Gerald switched to a new architecture. The previous
> version was just a plain Perl module loaded as a handler by mod_perl.
> This version is also an Apache module.
Okay, if it's only in the recent betas then it's possible that only a
few people have enc
At 4:18 PM -0500 3/22/02, Perrin Harkins wrote:
>Modules loaded with PerlModule and PerlRequire are not supposed to
>be loaded again the second time. I seem to remember that they are
>loaded again when using DSO though, so if you're using DSO you may
>want to recompile as static. Also, if you
Kee Hinckley wrote:> 1. *Why* are the apache config files executed twice (completely
with
> loading and unloading all the modules)?
This is a core apache thing. Apache does it to verify that a restart is
safe. See
http://thingy.kcilink.com/modperlguide/config/Apache_Restarts_Twice_On_Start.
At 11.00 -0500 11/21/2001, Perrin Harkins wrote:
>
>
>David, are you using Apache::ReadConfig or anything that uses it?
>
>- Perrin
Nope, not using ReadConfig. And to address another point, the behavior is consistant
regardless of whether or not PerlFreshRestart is on.
David
ok, here was my test...
[geoff@mainsheet apache]$ diff -u conf/httpd.conf.default conf/httpd.conf
--- conf/httpd.conf.default Wed Nov 21 02:00:16 2001
+++ conf/httpd.conf Wed Nov 21 11:59:35 2001
@@ -38,6 +38,8 @@
# server as "/usr/local/apache/logs/foo.log".
#
+PerlModule My::Foo
+
> -Original Message-
> From: Perrin Harkins [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, November 21, 2001 11:12 AM
> To: Geoffrey Young; [EMAIL PROTECTED]; David Pisoni
> Subject: Re: PerlModule not updating %INC
>
>
> > IIRC, I ran a test with only h
> IIRC, I ran a test with only httpd.conf.default with only these additions
>
> PerlModule My::Foo
>
> then
>
> package My::Foo;
> warn "initializing...";
>
>
> in lib/perl and I got 'initializing' on each restart. no
Apache::ReadConfig
> going on here.
And no PerlFreshRestart?
> -Original Message-
> From: Perrin Harkins [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, November 21, 2001 11:01 AM
> To: Geoffrey Young; [EMAIL PROTECTED]; David Pisoni
> Subject: Re: PerlModule not updating %INC
>
>
> > I wonder if this has something t
> I wonder if this has something to do with the multiple init thing
>
> http://marc.theaimsgroup.com/?l=apache-modperl&m=100510779912574&w=2
It does. It's exactly the same bug.
> if the interpreter is really being entirely broken down on each restart
> (including the initial one that Apache doe
> -Original Message-
> From: Perrin Harkins [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, November 20, 2001 6:43 PM
> To: David Pisoni; [EMAIL PROTECTED]; Robert Landrum
> Subject: Re: PerlModule not updating %INC
>
[snip]
>
> It sounds like this is a real bug wi
At 18.32 -0500 11/20/2001, Robert Landrum wrote:
>> >If that is the case, My::Special::Module won't be loaded and compiled until the
>very first time that someone hits /whatever.
>>
>>Just about EVERY module we use has a 'PerlModule' call to it, outside any enclosing
>blocks. Although I do have
> If you preload, It's not going to put the module into %INC.
> Otherwise Apache::StatINC would intentionally overwrite that shared
> memory and destroy the purpose for using PerlModule in the first
> place.
...and that's why you shouldn't use StatINC on a production server. There
is no magic ab
>
> >If that is the case, My::Special::Module won't be loaded and
>compiled until the very first time that someone hits /whatever.
>
>Just about EVERY module we use has a 'PerlModule' call to it,
>outside any enclosing blocks. Although I do have 'PerlHandler'
>directives in and blocks, the m
At 18.02 -0500 11/20/2001, Robert Landrum wrote:
>At 2:31 PM -0800 11/20/01, David Pisoni wrote:
>> >We have been doing development using mod_perl, but finding that Apache::StatINC
>was not working as expected (i.e., we needed to restart the web server in order to
>see our module changes in effe
At 2:31 PM -0800 11/20/01, David Pisoni wrote:
> >We have been doing development using mod_perl, but finding that
>Apache::StatINC was not working as expected (i.e., we needed to
>restart the web server in order to see our module changes in
>effect.) Our apache config files preload all necessa
not
>appear in Apache::Status "loaded modules" page, but do appear in the Inheritance tree.
>
>Ideas?
>
>Thanks,
>David
>
>>Date: Thu, 18 Oct 2001 12:57:27 -0800
>>To: Stas Bekman <[EMAIL PROTECTED]>
>>From: David Pisoni <[EMAIL PROTECTED
atus "loaded modules" page, but do appear in the Inheritance tree.
Ideas?
Thanks,
David
>Date: Thu, 18 Oct 2001 12:57:27 -0800
>To: Stas Bekman <[EMAIL PROTECTED]>
>From: David Pisoni <[EMAIL PROTECTED]>
>Subject: Re: PerlModule not updating %INC
>Cc: Perri
At 1.13 +0800 10/17/2001, Stas Bekman wrote:
>David Pisoni wrote:
>
>>>At 18.23 -0400 10/11/2001, Perrin Harkins wrote:
>>>
>At 18.07 -0400 10/11/2001, Perrin Harkins wrote:
>
>>>We are using perl 5.6.0 for Apache 1.3/20, with mod_perl 1.26.
>>>
>>Are you sure? There was a pro
David Pisoni wrote:
>>At 18.23 -0400 10/11/2001, Perrin Harkins wrote:
>>
At 18.07 -0400 10/11/2001, Perrin Harkins wrote:
>>We are using perl 5.6.0 for Apache 1.3/20, with mod_perl 1.26.
>>
>Are you sure? There was a problem with %INC and PerlModule, but I
>
>>>thought
>At 18.23 -0400 10/11/2001, Perrin Harkins wrote:
>> > At 18.07 -0400 10/11/2001, Perrin Harkins wrote:
>> > > > We are using perl 5.6.0 for Apache 1.3/20, with mod_perl 1.26.
>> > >
>> > >Are you sure? There was a problem with %INC and PerlModule, but I
>>thought
>> > >it was fixed in 1.26.
>> >
At 18.23 -0400 10/11/2001, Perrin Harkins wrote:
> > At 18.07 -0400 10/11/2001, Perrin Harkins wrote:
>> > > We are using perl 5.6.0 for Apache 1.3/20, with mod_perl 1.26.
>> >
>> >Are you sure? There was a problem with %INC and PerlModule, but I
>thought
>> >it was fixed in 1.26.
>> >
>> >- Perr
> At 18.07 -0400 10/11/2001, Perrin Harkins wrote:
> > > We are using perl 5.6.0 for Apache 1.3/20, with mod_perl 1.26.
> >
> >Are you sure? There was a problem with %INC and PerlModule, but I
thought
> >it was fixed in 1.26.
> >
> >- Perrin
>
> Indeed, like I said, I tested it by dumping %INC my
At 18.07 -0400 10/11/2001, Perrin Harkins wrote:
> > We are using perl 5.6.0 for Apache 1.3/20, with mod_perl 1.26.
>
>Are you sure? There was a problem with %INC and PerlModule, but I thought
>it was fixed in 1.26.
>
>- Perrin
Indeed, like I said, I tested it by dumping %INC myself -- the modul
> We are using perl 5.6.0 for Apache 1.3/20, with mod_perl 1.26.
Are you sure? There was a problem with %INC and PerlModule, but I thought
it was fixed in 1.26.
- Perrin
Stas Bekman wrote:
>
> On Thu, 23 Aug 2001, Rasoul Hajikhani wrote:
>
> > ___cliff rayman___ wrote:
> > >
> > > and what do the error logs say?
> > >
> > > Rasoul Hajikhani wrote:
> > >
> > > > I know this question will sound primitive to most of you, however, I
> > > > have this nagging error w
Ken Williams wrote:
>
> [EMAIL PROTECTED] (Rasoul Hajikhani) wrote:
> >> > "use lib qw(...);". I have tried declaring:
> >> > "use MY::Perl::Control::WebAccess;" in my startup.pl, with the same
> >
> >Here it is:
> >
> >Undefined subroutine &My::Perl::Control::WebAccess::handler called.
>
> Look
[EMAIL PROTECTED] (Rasoul Hajikhani) wrote:
>> > "use lib qw(...);". I have tried declaring:
>> > "use MY::Perl::Control::WebAccess;" in my startup.pl, with the same
>
>Here it is:
>
>Undefined subroutine &My::Perl::Control::WebAccess::handler called.
Looks like you need to check the capitalizati
On Thu, 23 Aug 2001, Rasoul Hajikhani wrote:
> ___cliff rayman___ wrote:
> >
> > and what do the error logs say?
> >
> > Rasoul Hajikhani wrote:
> >
> > > I know this question will sound primitive to most of you, however, I
> > > have this nagging error which won't go away.
> > > In my httpsd.con
___cliff rayman___ wrote:
>
> and what do the error logs say?
>
> Rasoul Hajikhani wrote:
>
> > I know this question will sound primitive to most of you, however, I
> > have this nagging error which won't go away.
> > In my httpsd.conf, I have declared "PerlModule
> > MY::Perl::Control::WebAcce
and what do the error logs say?
Rasoul Hajikhani wrote:
> I know this question will sound primitive to most of you, however, I
> have this nagging error which won't go away.
> In my httpsd.conf, I have declared "PerlModule
> MY::Perl::Control::WebAccess" which I know is where it is supposed to
>
> My apache server does not start up when I add
> PerlModule B::TerseSize
> to the httpsd.conf file. Or any "PerlModule" flag. Any one can tell me
> why? I am trying to determine a leakage in my script...
Do you have B::TerseSize installed on your system? It's not a standard
module. Check your
On 22 Aug 2000, Andrew Gideon wrote:
...
> My .htaccess file contains:
>
> PerlModule Apache::TAGXSessionAuth
> PerlAuthenHandler Apache::TAGXSessionAuth->authen
> PerlAuthzHandlerApache::TAGXSessionAuth->authz
>
> After attaching to a child process and getti
On Thu, 16 Dec 1999 [EMAIL PROTECTED] wrote:
> hi,
>
> I was wondering why the PerlModule and perlRequire didn't work for me.
> I have a fresh installation of :
> apache 1.3.9 + mod_perl 1.21 (that is bundled in RedHat6.1),
> what was my surprise to see that when I try to use something like :
>
This is the same problem I've been struggling with.
What has fixed it for me is building Apache and mod_perl from the tar
archives and linking Apache statically (no .so's).
I haven't investigated much further, but even after I built Perl, Apache,
and mod_perl by hand it still happened. Only w
46 matches
Mail list logo
