. 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:
cfr Hi list,
cfr One questions for the braves ;-)
cfr As I understand, the directive
cfr
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
cfr
of thing shouldn't happen unless you
request it.
Perhaps some options passed to PerlModule though adding (...) doesn't help
since PerlModule expects a list of modules.
There's no way it could since PerlModule has no way of knowing what
namespaces you are going to want polluted.
- Perrin
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 braves ;-)
cfr As I understand, the directive
cfr PerlModule Foo::Bar
cfr
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
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
[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
-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:
loads the module but doesn't import the symbols
Hi list,
One questions for the braves ;-)
As I understand, the directive
PerlModule Foo::Bar
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.
Is there other way to load
' of the PerlModules
included through PerlModule in various virtualhosts. Other modules work.
These packages all run with strict and do not include any XS besides what
may hide under the cover with DBI, Date::Calc and Template. I also have a
headache. The packages were happily being included into my old build
faults with 'some' of the PerlModules
included through PerlModule in various virtualhosts. Other modules work.
These packages all run with strict and do not include any XS besides what
may hide under the cover with DBI, Date::Calc and Template. I also have a
headache. The packages were happily
Nikolaus Rath wrote:
Hallo!
Is it possible that PerlModule doesn't modify %INC?
With PerlModule CGI in the Apache configuration, all scripts with use
CGI produce warnings like:
Subroutine put redefined at /usr/lib/perl5/5.6.1/CGI.pm line 517.
Subroutine print redefined at /usr/lib
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
recompile
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 the
/Apache_Restarts_Twice_On_Start.html
I'm not saying I think it's the greatest idea, but that's the reason
behind it.
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
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
encountered this. Can anyone else who has built a
module with custom conf directives comment on this issue?
Maybe we need an option for PerlModule that forces a load each time?
It seems like something to keep the C and perl sides doing the same
thing is what's needed, so that if the C stuff gets
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 then
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
-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 with PerlModule
I wonder if this has something to do with the multiple init thing
http://marc.theaimsgroup.com/?l=apache-modperlm=100510779912574w=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 does when
-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 to do with the multiple init thing
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:12 AM
To: Geoffrey Young; [EMAIL PROTECTED]; David Pisoni
Subject: Re: PerlModule not updating %INC
IIRC, I ran a test with only httpd.conf.default with only
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
At 11.00 -0500 11/21/2001, Perrin Harkins wrote:
SNIP
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
Red-Hat Linux (7.1) Perl 5.6.1 / Apache 1.3.20 / mod_perl 1.26
Problem : PerlModule does not cause %INC to be updated, but 'use' does
Symptoms : Apache::StatINC does not work for said modules. Said modules do not
appear in Apache::Status loaded modules page, but do appear in the Inheritance
modules at
start time using the 'PerlModule' directive. When I started peeking
through Apache::Status I found that although all of our loaded
modules appear in the Inheritance Tree and the ISA Tree, most of
them did not appear in the Loaded Modules section. (I also did a
test handler
.) Our apache config files preload all necessary
modules at start time using the 'PerlModule' directive. When I started peeking
through Apache::Status I found that although all of our loaded modules appear in the
Inheritance Tree and the ISA Tree, most of them did not appear in the Loaded
Modules
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 Location and Files blocks
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
hi guys...
I know this is from a while ago, but I'm still seeing the double init
thing with PerlModule and PerlRequire on server restarts. I've tried two
different 5.6.1 installs with current CVS.
can somebody verify that I'm not seeing things? the test I was using was
the default
/ Apache 1.3.20 / mod_perl 1.26
Red-Hat Linux (7.1) Perl 5.6.1 / Apache 1.3.20 / mod_perl 1.26
Problem : PerlModule does not cause %INC to be updated, but 'use' does
Symptoms : Apache::StatINC does not work for said modules. Said modules do not appear
in Apache::Status loaded modules
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 problem with %INC and PerlModule, but I
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
it was fixed in 1.26.
- Perrin
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.
- Perrin
Indeed
in order to see our
module changes in effect.) Our apache config files preload all necessary modules at
start time using the 'PerlModule' directive. When I started peeking through
Apache::Status I found that although all of our loaded modules appear in the
Inheritance Tree and the ISA Tree, most
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
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 modules
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
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.
- Perrin
Indeed, like I
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.
Looks like you need to check
.
In my httpsd.conf, I have declared PerlModule
MY::Perl::Control::WebAccess which I know is where it is supposed to
be. My @INC does not include the path to that directory, however, in my
startup.pl I have that directory as my
use lib qw(...);. I have tried declaring:
use MY::Perl
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
be. My @INC does not include the path to that directory, however
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
___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::WebAccess which I
PerlModule
MY::Perl::Control::WebAccess which I know is where it is supposed to
be. My @INC does not include the path to that directory, however, in my
startup.pl I have that directory as my
use lib qw(...);. I have tried declaring:
use MY::Perl::Control::WebAccess; in my startup.pl
[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 capitalization on 'MY'.
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...
thanks
-r
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have recently been working on a framework for moving our applications to
mod_perl but I've run into a very odd problem.
I load our program's main Apache handler, with:
PerlModule IQGroup::IQCoordinator
And then set it up
There have been some messages on the Mason list about people experiencing
startup.pl being loaded twice, even without PerlFreshRestart on. I know the
server restarts during startup, but PerlRequire and PerlModule are both
supposed to obey the laws of %INC, right? I seem to remember some
On Mon, 6 Aug 2001, Perrin Harkins wrote:
There have been some messages on the Mason list about people experiencing
startup.pl being loaded twice, even without PerlFreshRestart on. I know the
server restarts during startup, but PerlRequire and PerlModule are both
supposed to obey the laws
I was using Apache::Status to learn a bit about what is loaded by my
server, and I am wondering about a detail...
If I put this:
Perl
use Apache::Foo;
/Perl
Or this:
PerlModule Apache::Foo
I would expect the two to behave the same, but they don't! The "use" in
the Perl section
I've noticed an inconcistency between PerlModule and use() (and
PerlRequire and require()).
When Apache starts, it immediately restarts itself to see whether it can
sustain the reload. So when you have
PerlModule Apache::Registry
you will see:
Subroutine handler redefined at
/usr/lib/perl5
Problem: I configure apache and mod_perl. One day it runs fine. The next
day I stop and start
the server and get a 'Apache.pm failed' problem. I looked at the web site
and found I needed to
add ' PerlModule Apache' to my httpd.conf file. I get the error message
listed below. I looked
is a
part of apache.
but in addition.
how do i start writing perl so as to take advantage of modperl better..??
Plus can anyone explain to me the semantics/usage of the following in my httpd.conf
and how i can change it to suit me better.
PerlModule Apache::Registry
Location /perl
SetHandler perl
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 getting
mgraham ([EMAIL PROTECTED]) said something to this effect:
With the above I expect to be able to call the following in some
handler:
Foo::load_var()
...and $PACKAGE_LEXICAL should still be 'wubba'.
...Except that by calling Foo:load_var() you are setting $PACKAGE_LEXICAL
to undef (by
to call Foo::set_var('wubba') from startup.pl, and
then call Foo::do_stuff() from some child process.
The weird thing is, this works as I expect when I put "PerlModule Foo"
in httpd.conf, but not when I put "use Foo;" in startup.pl.
Does everybody else use PerlModule to p
On Fri, 4 Aug 2000, darren chamberlain wrote:
Sharing a variable among children is difficult; you need to use IPC::Sharable
or something similar.
Not if it's read-only after the fork, which this one appears to be. You
can load it with a value at startup and it will be shared.
- Perrin
On Sun, 30 Jul 2000, mgraham wrote:
Under mod_perl, I find inconsistent behaviour. It works fine when a
module is loaded via the PerlModule directive in httpd.conf. However
when a module is loaded via startup.pl, the package lexicals "forget"
their values between calls.
[...]
T
Perrin Harkins wrote:
This sounds like a bad interaction with PerlFreshRestart and closure
variables. Does it work if you turn off PerlFreshRestart?
Can you live
with that?
Yes! It works with PerlFreshRestart Off. I think you're right - it
probably has something to do with the timing
On Fri, 4 Aug 2000, mgraham wrote:
Why should PerlFreshRestart be on, anyway? Ostensibly, it's so you
can make sure that your modules can survive a soft restart, but can't
you also gather that from 'apachectl graceful'?
With PerlFreshRestart turned off, a graceful restart will not reload
"PH" == Perrin Harkins [EMAIL PROTECTED] writes:
PH On Fri, 4 Aug 2000, mgraham wrote:
Why should PerlFreshRestart be on, anyway? Ostensibly, it's so you
can make sure that your modules can survive a soft restart, but can't
you also gather that from 'apachectl graceful'?
PH With
mod_perl, I find inconsistent behaviour. It works fine when a
module is loaded via the PerlModule directive in httpd.conf. However
when a module is loaded via startup.pl, the package lexicals "forget"
their values between calls.
# Foo.pm
package Foo;
use strict;
my $PACKA
On Sun, 30 Jul 2000, mgraham wrote:
Normally, I expect that lexical 'my' vars declared at the package
scope (i.e. at the top of a file), should be visible to subroutines
declared in the same package, and should maintain their values between
calls to those subroutines.
If you are running
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
when I switch to a non-DSO
Apache did it work for me.
-bill
At 03:39 PM 12/16/99 +, [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
Thanks a lot, Randy!!! I recompiled mod_perl with that flag, and now
PerlModule/PerlRequire/Use ...
work! Apache comes up, and everything seems fine so far! But I don't know
how this flag
influences whatever.
Apache loads all APache modules twice. This flag disables all PerlRequire
Have you been able to install it as a NT Service? I can only run
1.3.9/1.2.21 from the command line. 1.3.6/1.2.21 are working fine.
:( I hate NT.
John
[EMAIL PROTECTED]
Have you been able to install it as a NT Service? I can only run
1.3.9/1.2.21 from the command line. 1.3.6/1.2.21 are working fine.
:( I hate NT.
Did you try to compile mod_perl with
#define PERL_STARTUP_DONE_CHECK 1
at the top of the mod_perl.h? This may solve your problem.
Gerald
Did you try to compile mod_perl with
#define PERL_STARTUP_DONE_CHECK 1
at the top of the mod_perl.h? This may solve your problem.
Yes, without that define, DBI breaks and I can't run from the
command line without -X
Very frustrating, but no more so than the typical experience of
using
Yes, without that define, DBI breaks and I can't run from the
command line without -X
Very frustrating, but no more so than the typical experience of
using NT.
Did you first uninstall the old one (Apache -u), before installing the new
one? Does the error log contains any hints?
Gerald
chter" [EMAIL PROTECTED]
cc: [EMAIL PROTECTED] (bcc: John Arnold/DTC)
Subject: Re: Win32+PerlModule works !!!
Did you try to compile mod_perl with
#define PERL_STARTUP_DONE_CHECK 1
at the top of the mod_perl.h? This may solve your problem.
Yes, without that define, DBI breaks and I
- Original Message -
From: John D Groenveld [EMAIL PROTECTED]
To: Rolf Ohnmacht [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Wednesday, December 15, 1999 4:24 PM
Subject: Re: Win32+PerlModule works !!!
Have you been able to install it as a NT Service? I can only run
1.3.9/1.2.21
- Original Message -
From: Randy Kobes [EMAIL PROTECTED]
To: Rolf Ohnmacht [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Tuesday, December 14, 1999 2:32 AM
Subject: Re: Win32+modperl+EmbPerl - some questions ...
1.) 'PerlModule' ( eg. srm.conf ) or 'use HTML::Embperl' ( startup.pl
2.95.2 19991024
perl 5.005_03
When starting an httpd process with a 'PerlModule' defined in the conf file,
the process will seg fault when it attempts to fork:
open("/opt/apache/logs/access_log", O_WRONLY|O_APPEND|O_CREAT, 0644) = 3
fcntl(3, F_DUPFD, 0x000F)
Tony Demark wrote:
I have compiled the following:
Apache 1.3.9
mod_perl 1.21 (PERL_AUTHEN PERL_LOG PERL_STACKED_HANDLERS)
[cut]
When starting an httpd process with a 'PerlModule' defined in the conf file,
the process will seg fault when it attempts to fork:
[cut
I have compiled the following:
Apache 1.3.9
mod_perl 1.21 (PERL_AUTHEN PERL_LOG PERL_STACKED_HANDLERS)
on:
Ultra 10
Solaris 7
with:
gcc 2.95.2 19991024
perl 5.005_03
When starting an httpd process with a 'PerlModule' defined in the conf file
80 matches
Mail list logo
