On Tue, 3 Jul 2001, James G Smith wrote:
The current code I have uses %INC, but I wanted to write
something like the following:
sub use : immediate {
# do stuff here if logging
return CORE::use(@_);
}
you could just override CORE::GLOBAL::require. you don't need to
override the
How can I tell if a module is compiled and loaded into the memory properly
when the server starts?
Would it not be loaded even if I have put use My::ModuleName in the
startup.pl?
Bird
On Thu, 5 Jul 2001, Bird Lei wrote:
How can I tell if a module is compiled and loaded into the memory properly
when the server starts?
Would it not be loaded even if I have put use My::ModuleName in the
startup.pl?
use the Apache::Status module and read http://perl.apache.org/guide
Thanks.
At 11:56 AM 2001/7/5 +0800, Stas Bekman wrote:
On Thu, 5 Jul 2001, Bird Lei wrote:
How can I tell if a module is compiled and loaded into the memory properly
when the server starts?
Would it not be loaded even if I have put use My::ModuleName in the
startup.pl?
use the
James G Smith [EMAIL PROTECTED] said something to this effect on 07/02/2001:
How would something like this do:
NAME
Apache::Use
SYNOPSIS
use Apache::Use (Logger = DB, File = /www/apache/logs/modules);
DESCRIPTION
Apache::Use will record the modules used over the course
darren chamberlain [EMAIL PROTECTED] wrote:
James G Smith [EMAIL PROTECTED] said something to this effect on 07/02/2001:
How would something like this do:
NAME
Apache::Use
SYNOPSIS
use Apache::Use (Logger = DB, File = /www/apache/logs/modules);
DESCRIPTION
Apache::Use
. However, you lose information about which
modules are needed more often than others. There's no difference
between all scripts needing CGI.pm and one script needing
Foo::Bar.
Good point.
We also lose timing information. If 90% of the modules are
loaded into the process with the last
On Tuesday 03 July 2001 16:46, darren chamberlain wrote:
James G Smith [EMAIL PROTECTED] said something to this effect:
The current code I have uses %INC, but I wanted to write
something like the following:
sub use : immediate {
# do stuff here if logging
return CORE::use(@_);
darren chamberlain [EMAIL PROTECTED] wrote:
James G Smith [EMAIL PROTECTED] said something to this effect on 07/03/2001:
sub use : immediate {
# do stuff here if logging
return CORE::use(@_);
}
To go OT here, what would 'immediate' be doing here, if Perl
supported it?
It would be run at
How would something like this do:
NAME
Apache::Use
SYNOPSIS
use Apache::Use (Logger = DB, File = /www/apache/logs/modules);
DESCRIPTION
Apache::Use will record the modules used over the course of the
Perl interpreter's lifetime. If the logging module is able, the
old logs are read
out having to change it for
each site. For the life of me I cannot figure out how it's done in mod_perl
without having namespace problems...
I read that you should use a module, but then I understand you cannot have
modules with the same name.I readyou could alsogive package
name in the configure.cgi sc
]]
Sent: 2001Äê7ÔÂ2ÈÕ 13:18
To: [EMAIL PROTECTED]
Subject: requre,use, modules, namespace...I'm confused...
Hi,
I've read the docs on traps in using require and use, etc in
mod_perl...I'm confused
heres what I'm trying to figure out...
lets say I have 3 sites on 1 box. so I have /home/httpd
Hello,
I am using mod-perl, and I am in the development stages of coding. Each time
I make a code change to a module, I must restart apache. I know there must
be docs for this, but I cannot find them from the apache web site. Could
someone assist me in finding those? Or if someone knows of a
the packages to the script which would otherwise use them during
development so that they get recompiled every time. This wouldn't
work very well if you are sharing the modules between a bunch of
programs, obviously, but if you are trying to debug something it
might help.
Tim
dougm 01/06/18 19:38:55
Modified:src/modules/perl mod_perl.c
Log:
removing dead code
Revision ChangesPath
1.139 +0 -23 modperl/src/modules/perl/mod_perl.c
Index: mod_perl.c
===
RCS file
dougm 01/06/18 20:12:48
Modified:.Makefile.PL
src/modules/perl mod_perl.c mod_perl.h perl_config.c
Log:
remove dead code for PERL_STARTUP_{IS_DONE,DONE_CHECK} hack
Revision ChangesPath
1.187 +0 -2 modperl/Makefile.PL
Index
dougm 01/06/13 21:36:22
Modified:.Changes
t/net/perl api.pl
src/modules/perl Apache.xs
Log:
$r-custom_response($code, undef) will now unset the current CustomResponse
Revision ChangesPath
1.595 +3 -0 modperl/Changes
dougm 01/06/13 22:26:29
Modified:.Changes
src/modules/perl Apache.xs
Log:
croak if the filehandle passed to $r-send_fd is NULL
Revision ChangesPath
1.598 +3 -0 modperl/Changes
Index: Changes
dougm 01/06/12 13:45:38
Modified:.Changes
src/modules/perl apache_inc.h
Log:
win32 fixes for apache 1.3.20
Revision ChangesPath
1.593 +2 -0 modperl/Changes
Index: Changes
dougm 01/05/22 15:13:28
Modified:src/modules/perl modperl_callback.c
Log:
bug fix: callbacks that returned DECLINED were changed to OK
Revision ChangesPath
1.42 +2 -1 modperl-2.0/src/modules/perl/modperl_callback.c
Index: modperl_callback.c
Hi,
I'm using mod_perl without the registry, because it seems a bit faster
and, well, more elegant. This means, in essence, that the configuration
is:
PerlInitHandler Apache::StatINC
PerlSetEnv PERL5LIB /home/burkhold/perl/local/share/perl/5.6.0
Location /burkhold/foo
SetHandler
Whoops. Pilot error. Cancel that. Sorry.
//Thomas
Thomas K. Burkholder wrote:
Hi,
I'm using mod_perl without the registry, because it seems a bit faster
and, well, more elegant. This means, in essence, that the configuration
is:
PerlInitHandler Apache::StatINC
PerlSetEnv PERL5LIB
dougm 01/05/14 14:22:37
Modified:src/modules/perl modperl_types.h
Log:
fix for non-ithread Perls
Revision ChangesPath
1.42 +2 -0 modperl-2.0/src/modules/perl/modperl_types.h
Index: modperl_types.h
dougm 01/05/09 10:04:36
Modified:src/modules/perl modperl_options.c
Log:
ithread only option check should only be done on server config, not per-dir
Revision ChangesPath
1.7 +1 -1 modperl-2.0/src/modules/perl/modperl_options.c
Index: modperl_options.c
From: Paul Lindner, on Tuesday, May 01, 2001 3:04 AM:
On a related note, does anyone anywhere still use
Experimental::Exception?
The COPE CORBA module uses Experimental::Exception for it's exception
handling. There is an effort underway to change to Error.pm (or something
else a bit more
[1] for my Perl exception package (yes, another one :) which, in its
development version, now mostly does the Right Thing for mod_perl. See
http://sourceforge.net/projects/perlexception/ for the curious.
Since I'm doing the mod_perl exception handling talk at TPC, I feel
obligated to ask
On Mon, 30 Apr 2001, Matt Sergeant wrote:
[1] for my Perl exception package (yes, another one :) which, in its
development version, now mostly does the Right Thing for mod_perl. See
http://sourceforge.net/projects/perlexception/ for the curious.
Since I'm doing the mod_perl exception
On Mon, 30 Apr 2001, Jeffrey W. Baker wrote:
On Mon, 30 Apr 2001, Matt Sergeant wrote:
[1] for my Perl exception package (yes, another one :) which, in its
development version, now mostly does the Right Thing for mod_perl. See
http://sourceforge.net/projects/perlexception/ for
On Mon, 30 Apr 2001, Matt Sergeant wrote:
On Mon, 30 Apr 2001, Jeffrey W. Baker wrote:
On Mon, 30 Apr 2001, Matt Sergeant wrote:
[1] for my Perl exception package (yes, another one :) which, in its
development version, now mostly does the Right Thing for mod_perl. See
On Mon, 30 Apr 2001, Jeffrey W. Baker wrote:
Yes precisely. It used to be that you could only die() with a string, but
5.mumble gave us die() with a reference to an object and at that moment
the system was complete. The creation of a rational exception object type
is left to the discretion
Matt Sergeant [EMAIL PROTECTED] wrote:
It doesn't seem any different from Error.pm to me, except in syntax.
Maybe you could expand on why/where it is different?
OK, yes, it *is* very similar in principle - I would perhaps have been
better to have added to Graham's code, but I suffer from
On Mon, 30 Apr 2001, Matt Sergeant wrote:
On Mon, 30 Apr 2001, Jeffrey W. Baker wrote:
Yes precisely. It used to be that you could only die() with a string, but
5.mumble gave us die() with a reference to an object and at that moment
the system was complete. The creation of a rational
Title: RE: Exception modules
unsubscribe please- thanks
-Original Message-
From: Matt Sergeant [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 30, 2001 4:29 PM
To: Jeffrey W. Baker
Cc: [EMAIL PROTECTED]
Subject: Re: Exception modules
On Mon, 30 Apr 2001, Jeffrey W. Baker wrote
On Mon, 30 Apr 2001, Jeffrey W. Baker wrote:
I have learned that errors from down in the call stack are very rarely
conditionally recoverable. If I call obj-method(), and it throws an
exception, there are few situations where the cause of the exception
matters at all. In most cases I will
At 03:24 PM 4/30/01 -0700, Jeffrey W. Baker wrote:
On Mon, 30 Apr 2001, Matt Sergeant wrote:
On Mon, 30 Apr 2001, Jeffrey W. Baker wrote:
Yes precisely. It used to be that you could only die() with a
string, but
5.mumble gave us die() with a reference to an object and at that
On Mon, 30 Apr 2001, Jeffrey W. Baker wrote:
type of exception. Right now I cannot in fact think of
any program I have written that branches on the type of
exception. Java encourages this with multiple catch
in CP Web Mail, the underlying libraries throw typed
exceptions so that the
On Mon, Apr 30, 2001 at 05:47:03PM -0700, brian moseley wrote:
On Mon, 30 Apr 2001, Jeffrey W. Baker wrote:
type of exception. Right now I cannot in fact think of
any program I have written that branches on the type of
exception. Java encourages this with multiple catch
in CP Web
on 4/30/01 8:47 PM, brian moseley at [EMAIL PROTECTED] wrote:
On Mon, 30 Apr 2001, Jeffrey W. Baker wrote:
type of exception. Right now I cannot in fact think of
any program I have written that branches on the type of
exception. Java encourages this with multiple catch
in CP Web Mail,
On Mon, 30 Apr 2001, Perrin Harkins wrote:
I've tried that, but last time I went with more general
classes of exceptions containing unique error IDs
(defined in a constants module) to indicate the exact
type. Not as Java-like, but it did save me from
creating dozens of classes with no
dougm 01/04/30 18:53:53
Modified:src/modules/perl modperl_global.h
Log:
fix for non-threaded Perls
Revision ChangesPath
1.2 +2 -0 modperl-2.0/src/modules/perl/modperl_global.h
Index: modperl_global.h
dougm 01/04/29 21:38:37
Modified:src/modules/perl mod_perl.c mod_perl.h modperl_types.h
Log:
integrate modperl_global module and initialize pconf/request_rec globals
Revision ChangesPath
1.51 +13 -0 modperl-2.0/src/modules/perl/mod_perl.c
Index
any problem.
It dumps core giving segmentation fault when i try to load modules with
startup.pl file.
I figure it out that I can't load any module which have .so file with my
startup.pl. I have also tried with mensioning proper location for those modules.
But everytime it give segmentation fault
On Wed, Apr 25, 2001 at 11:34:53AM -0700, Mohammed Azam wrote:
perl 5.00503
mod_perl 1.22
apache 1.3.12
aix 4.3.3
That appears to be an unfortunate combination that does not work
properly. Get APache 1.3.19, perl 5.6.1 and the newest modperl from CVS
and the patch I did mention here a few
dougm 01/04/25 09:19:45
Modified:src/modules/perl mod_perl.c
Log:
fix #ifndef USE_ITHREADS
Revision ChangesPath
1.50 +1 -1 modperl-2.0/src/modules/perl/mod_perl.c
Index: mod_perl.c
dougm 01/04/24 22:27:17
Modified:src/modules/perl modperl_interp.c modperl_util.c
modperl_util.h
Log:
use apr_os_dso_handle_put/apr_dso_unload rather than the unportable dlclose()
Revision ChangesPath
1.32 +1 -1 modperl-2.0/src
dougm 01/04/23 22:10:41
Modified:src/modules/perl modperl_types.h
Log:
allow MP_IOBUFSIZE to be -D defined
Revision ChangesPath
1.37 +6 -4 modperl-2.0/src/modules/perl/modperl_types.h
Index: modperl_types.h
dougm 01/04/19 10:44:22
Modified:src/modules/perl mod_perl.c modperl_filter.c
modperl_filter.h
Log:
register/run PerlInputFilterHandlers
Revision ChangesPath
1.48 +30 -2 modperl-2.0/src/modules/perl/mod_perl.c
Index: mod_perl.c
dougm 01/04/19 10:57:17
Modified:src/modules/perl modperl_callback.c modperl_handler.c
modperl_handler.h
Log:
move handler resolver code into modperl_handler_resolve routine
Revision ChangesPath
1.41 +3 -34 modperl-2.0/src/modules/perl
dougm 01/04/19 11:08:10
Modified:src/modules/perl mod_perl.c
Log:
tidy a bit
Revision ChangesPath
1.49 +12 -10modperl-2.0/src/modules/perl/mod_perl.c
Index: mod_perl.c
===
RCS file
dougm 01/04/19 17:43:47
Modified:src/modules/perl modperl_filter.c modperl_filter.h
Log:
remove dead code
Revision ChangesPath
1.16 +0 -11 modperl-2.0/src/modules/perl/modperl_filter.c
Index: modperl_filter.c
dougm 01/04/17 15:01:20
Modified:.Changes
src/modules/perl mod_perl.c
Log:
back out 'stop win32 crash when bringing down service' change, no
longer needed with 1.3.19
Revision ChangesPath
1.586 +4 -0 modperl/Changes
Index
On Wed, 7 Mar 2001, Ask Bjoern Hansen wrote:
On 6 Oct 2000 [EMAIL PROTECTED] wrote:
dougm 00/10/06 13:18:29
Modified:t/internal error.t
src/modules/perl mod_perl.c
Log:
more for the "Apache::send_http_header was resetting r-status = 200" f
dougm 01/04/17 21:37:47
Modified:src/modules/perl modperl_filter.c
Log:
pass the APR::Brigade to filter handlers
Revision ChangesPath
1.11 +1 -0 modperl-2.0/src/modules/perl/modperl_filter.c
Index: modperl_filter.c
dougm 01/04/12 18:10:21
Modified:src/modules/perl modperl_callback.c
Log:
log rather than trace failure to resolve handler
Revision ChangesPath
1.40 +3 -2 modperl-2.0/src/modules/perl/modperl_callback.c
Index: modperl_callback.c
dougm 01/04/11 15:48:29
Added: src/modules/perl modperl_const.c modperl_const.h
Log:
module for compiling/exporting constants
Revision ChangesPath
1.1 modperl-2.0/src/modules/perl/modperl_const.c
Index: modperl_const.c
dougm 01/04/11 16:11:03
Modified:src/modules/perl modperl_const.c
Log:
tab begone
Revision ChangesPath
1.3 +1 -1 modperl-2.0/src/modules/perl/modperl_const.c
Index: modperl_const.c
dougm 01/04/11 17:45:42
Modified:src/modules/perl modperl_const.c
Log:
only bleedperl newCONSTSUB returns a CV, older Perls are void
Revision ChangesPath
1.4 +4 -6 modperl-2.0/src/modules/perl/modperl_const.c
Index: modperl_const.c
dougm 01/04/11 17:58:00
Modified:src/modules/perl modperl_const.c
Log:
unused variable
Revision ChangesPath
1.5 +0 -2 modperl-2.0/src/modules/perl/modperl_const.c
Index: modperl_const.c
dougm 01/04/11 18:03:14
Modified:src/modules/perl mod_perl.c
Log:
i swear eric did this already
Revision ChangesPath
1.45 +1 -1 modperl-2.0/src/modules/perl/mod_perl.c
Index: mod_perl.c
dougm 01/04/11 20:01:40
Modified:t/apache constants.t
src/modules/perl modperl_const.c
Log:
allow name for imports
Revision ChangesPath
1.3 +3 -2 modperl-2.0/t/apache/constants.t
Index: constants.t
dougm 01/04/02 22:23:47
Modified:src/modules/perl modperl_callback.c
Log:
if handler is resolved at request time and not duped (prefork-mpm case), need to use
s-process-pconf pool
Revision ChangesPath
1.37 +12 -2 modperl-2.0/src/modules/perl
Hi there,
On Thu, 29 Mar 2001, Bolt Thrower wrote:
Can't locate object method "module" via package "Apache" at
/usr/lib/perl5/site_perl/5.005/Apache/DBI.pm line 202.
It seems that something doesn't like the Apache-module() call, which
wouldn't be available unless it's actually in a
On Thu, 29 Mar 2001, Bolt Thrower wrote:
I've got a working mod_perl installation on a Linux 2.2.14 /
Apache/1.3.17 (Unix) mod_perl/1.25 / perl 5.005_03 machine. I'm trying
to install Apache::AuthCookieDBI via my CPAN shell, and I keep getting
errors of the sort:
Can't locate object
my initial message. I like using the
CPAN shell to install my perl modules, but I suppose all the Apache
modules I try to install that rely on Apache::DBI will fail their
respective tests. So, the above command should probably be amended to:
perl -MCPAN -e "force install Apache::AuthCook
I've got a working mod_perl installation on a Linux 2.2.14 /
Apache/1.3.17 (Unix) mod_perl/1.25 / perl 5.005_03 machine. I'm trying
to install Apache::AuthCookieDBI via my CPAN shell, and I keep getting
errors of the sort:
Can't locate object method "module" via package "Apache" at
dougm 01/03/25 11:04:56
Modified:src/modules/perl modperl_mgv.c
Log:
prevent core dump if HvARRAY is NULL
Revision ChangesPath
1.9 +3 -0 modperl-2.0/src/modules/perl/modperl_mgv.c
Index: modperl_mgv.c
dougm 01/03/25 16:36:39
Modified:src/modules/perl modperl_interp.c
Log:
look higher up the chain for the interpreter to share across subrequests
Revision ChangesPath
1.29 +16 -4 modperl-2.0/src/modules/perl/modperl_interp.c
Index: modperl_interp.c
dougm 01/03/25 17:08:30
Modified:lib/ModPerl Code.pm
src/modules/perl modperl_config.c modperl_handler.c
modperl_handler.h modperl_mgv.c modperl_mgv.h
Log:
add support for proper merge of handlers
example:
PerlFixupHandler One::fixup
dougm 01/03/16 09:23:31
Modified:src/modules/perl modperl_callback.c modperl_callback.h
modperl_handler.c modperl_handler.h modperl_types.h
Log:
prototype the 3 pools in run_handlers() rather that use va_args,
so we can have a pool sooner rather than
dougm 01/03/16 22:08:05
Modified:src/modules/perl modperl_cmd.c
Log:
make use of modperl_handler_array_ macros
Revision ChangesPath
1.2 +2 -2 modperl-2.0/src/modules/perl/modperl_cmd.c
Index: modperl_cmd.c
dougm 01/03/15 21:08:15
Modified:lib/ModPerl Code.pm
src/modules/perl mod_perl.c modperl_callback.c
modperl_callback.h
Log:
use proper prefix for all modperl_callback_ functions
Revision ChangesPath
1.46 +1 -1 modperl
dougm 01/03/15 21:52:29
Modified:lib/ModPerl Code.pm
src/modules/perl mod_perl.c mod_perl.h modperl_config.c
modperl_config.h modperl_interp.c modperl_interp.h
Added: src/modules/perl modperl_cmd.c modperl_cmd.h
Log:
move cmd stuffs
dougm 01/03/15 22:32:15
Modified:lib/ModPerl Code.pm
src/modules/perl modperl_callback.c modperl_handler.c
modperl_handler.h
Log:
move some code into modperl_handler_lookup_handlers() so it can be reused for
{get,set,push}_handlers
dougm 01/03/15 22:35:18
Modified:src/modules/perl modperl_config.h
Log:
allow modperl_config_req_get() to not core-dump if r == NULL
Revision ChangesPath
1.23 +2 -2 modperl-2.0/src/modules/perl/modperl_config.h
Index: modperl_config.h
dougm 01/03/15 22:41:46
Modified:src/modules/perl modperl_callback.c modperl_handler.c
modperl_handler.h
Log:
need to return the address incase caller needs to initialize (e.g. push/set)
Revision ChangesPath
1.33 +4 -4 modperl-2.0/src
dougm 01/03/15 23:30:25
Modified:lib/ModPerl Code.pm
src/modules/perl modperl_config.c modperl_filter.c
modperl_handler.c modperl_mgv.c modperl_types.h
Log:
no need for modperl_{files,process,connection}_config_t
Revision Changes
dougm 01/03/14 00:22:51
Modified:src/modules/perl mod_perl.c modperl_config.c
modperl_config.h modperl_interp.c modperl_types.h
Log:
allow PerlInterpLifetime to be per-dir for subrequest and request lifetime
Revision ChangesPath
1.32 +3 -3
dougm 01/03/14 09:28:07
Modified:src/modules/perl modperl_callback.c modperl_callback.h
Log:
canonicalize MP_HANDLER_TYPE_ names
Revision ChangesPath
1.26 +17 -15modperl-2.0/src/modules/perl/modperl_callback.c
Index: modperl_callback.c
dougm 01/03/14 17:26:18
Modified:src/modules/perl modperl_mgv.c modperl_perl_includes.h
Log:
fixes to compile with non-ithreads 5.6.0 Perl
Revision ChangesPath
1.2 +3 -1 modperl-2.0/src/modules/perl/modperl_mgv.c
Index: modperl_mgv.c
dougm 01/03/14 17:55:44
Modified:src/modules/perl mod_perl.c modperl_gtop.c modperl_gtop.h
Log:
fixes to compile without MP_TRACE
Revision ChangesPath
1.34 +2 -0 modperl-2.0/src/modules/perl/mod_perl.c
Index: mod_perl.c
dougm 01/03/14 20:34:04
Modified:src/modules/perl mod_perl.c modperl_interp.c
Log:
need to PERL_SET_CONTEXT to parent perl in non-threaded mpms
give a little more trace info about interpreters in virtual hosts
Revision ChangesPath
1.36 +3 -2 modperl-2.0
dougm 01/03/14 23:04:41
Modified:src/modules/perl modperl_callback.c modperl_config.c
modperl_config.h modperl_interp.c modperl_types.h
Log:
support "PerlInterpLifetime handler"
Revision ChangesPath
1.29 +3 -5 modperl-2.0/s
dougm 01/03/14 23:21:14
Modified:src/modules/perl modperl_config.c
Log:
make per-dir merger do something more useful
Revision ChangesPath
1.24 +16 -6 modperl-2.0/src/modules/perl/modperl_config.c
Index: modperl_config.c
dougm 01/03/13 20:22:51
Modified:src/modules/perl mod_perl.c modperl_util.c modperl_util.h
Log:
add modperl_server_desc() function
add more trace details when initializing the interpreter pool
Revision ChangesPath
1.30 +25 -6 modperl-2.0/src/modules/perl
dougm 01/03/13 22:57:44
Modified:src/modules/perl modperl_interp.c
Log:
share selected Perl interpreter across sub-requests by default
Revision ChangesPath
1.21 +10 -5 modperl-2.0/src/modules/perl/modperl_interp.c
Index: modperl_interp.c
dougm 01/03/09 15:42:05
Added: src/modules/perl modperl_mgv.c modperl_mgv.h
Log:
module for pre-computing gv_fetchpv lookups of handlers
Revision ChangesPath
1.1 modperl-2.0/src/modules/perl/modperl_mgv.c
Index: modperl_mgv.c
dougm 01/03/09 15:42:28
Added: src/modules/perl modperl_pcw.c modperl_pcw.h
Log:
module for walking the parsed Apache configuration
Revision ChangesPath
1.1 modperl-2.0/src/modules/perl/modperl_pcw.c
Index: modperl_pcw.c
dougm 01/03/09 15:46:38
Modified:lib/ModPerl Code.pm
src/modules/perl mod_perl.c mod_perl.h modperl_callback.c
modperl_callback.h modperl_config.c
modperl_config.h modperl_filter.c modperl_interp.c
have to
'wing it' completely.
Current Apache releases contain the facility to build your httpd
executable with support for dynamically linked modules (DSO). This means
that your httpd executable no longer gets bigger with each successive module
added to it. This is accomplished via the 'apxs
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
I am having difficulty reading configuration commands from a .htaccess file.
I've modified Apache::RefererBlock so that it no longer shows a
forbidden error, but rather redirects a default URL. I need this to
apply to specific directories, but do not want the hassle of having
to modify the
Message-
From: Robert Landrum
To: [EMAIL PROTECTED]
Sent: 2/20/01 7:05 PM
Subject: htaccess files and modules
I am having difficulty reading configuration commands from a .htaccess
file.
I've modified Apache::RefererBlock so that it no longer shows a
forbidden error, but rather redirects
--- Original Message -
From: Randy Kobes [EMAIL PROTECTED]
To: Garry Heaton [EMAIL PROTECTED]
Cc: mod_Perl [EMAIL PROTECTED]
Sent: Monday, February 19, 2001 6:48 PM
Subject: Re: (beginner) Win32 installation / "Writing Apache Modules in
Perl C"
http://perl.apache.org/distribu
"Randy Kobes" [EMAIL PROTECTED] wrote:
http://perl.apache.org/distributions.html contains links to how to
install mod_perl via ActivePerl's ppm (Perl Package Manager), as
well as some other Apache::* modules. For starting out on Win32 this route
is probably the easiest, as ever
d_perl via ActivePerl's ppm (Perl Package Manager), as
well as some other Apache::* modules. For starting out on Win32 this route
is probably the easiest, as everything you need to get started
comes with the ppm distribution.
hmmm. Randy, I'm running your *other* mod_perl binary distributi
heers,
Rob
Visit our website at http://www.kalinabears.com.au
- Original Message -
From: Randy Kobes [EMAIL PROTECTED]
To: Sisyphus [EMAIL PROTECTED]
Cc: mod_Perl [EMAIL PROTECTED]
Sent: Tuesday, February 20, 2001 12:33 PM
Subject: Re: (beginner) Win32 installation / "Writing Apache Mo
- Original Message -
From: "David Kaufman" [EMAIL PROTECTED]
To: "Randy Kobes" [EMAIL PROTECTED]; "Garry Heaton"
[EMAIL PROTECTED]
Cc: "mod_Perl" [EMAIL PROTECTED]
Sent: Monday, February 19, 2001 1:49 PM
Subject: Re: (beginner) Win32 installat
Ref: using Win 98 / Apache 1.3.14 on c:\program files\apache group\apache /
Perl 5.6 on c:\perl
I'm trying to get a working Win32 installation of mod_perl using "Writing
Apache Modules with Perl and C" but, as with most O'Reilly Perl books, it's
written for a Unix audience. Apache si
On Mon, 19 Feb 2001, Garry Heaton wrote:
Ref: using Win 98 / Apache 1.3.14 on c:\program files\apache group\apache /
Perl 5.6 on c:\perl
I'm trying to get a working Win32 installation of mod_perl using "Writing
Apache Modules with Perl and C" but, as with most O'Reilly Perl b
dougm 01/02/18 13:55:08
Modified:src/modules/perl modperl_callback.c modperl_callback.h
Log:
avoid c++ keywords (class)
Revision ChangesPath
1.17 +1 -1 modperl-2.0/src/modules/perl/modperl_callback.c
Index: modperl_callback.c
401 - 500 of 748 matches
Mail list logo
