Hi!
In the code for DBD::Oracle::db::ping method there are lines
local $SIG{__DIE__};
local $SIG{__WARN__};
As I understand these lines don't do anything though I guess they are supposed
to suppress warning messages and possibly 'die' messages. Currently everytime
when ping fails and
I have an error on my server that I think is caused by an infinite loop in
perl code [*]. Does anyone have a reliable way to detect where this is
happening on a server with lots of code?
Matt.
--
:-Get a smart net/:-
[*] In case anyone was wondering, this is probably why you can't get to
Greetings.
This
documentationpatchaddressesthe single thread snafu
on Win32.
Comments, corrections and additions
(even subtractions) welcome. (Also on the hot topic of the day: where in the doc
does this fit?)
Cheers,
alf
modperl_multithread_NT.pod
Description: Binary data
Greetings.
[following Stas' suggestion I have subscribed to the list and
posted the patch there, so I am crossposting]
Do you know if FastCGI is multi-threaded or multi-process on
Windows?
Multi process. Each process speaks tomod_fastcgi over a
named pipe. As you mention, this (being
I'm having a bit of a problem getting everything to work right.
Everything Compiles, then it looks like it's running, but the moment
your client (or telnet) connects, it shuts itself down.
I've tried 'make clean make make install' to see if that remedies
the problem, but that doesn't help.
Hello,
I have a mod_cgi application, which we are currently in the process of
converting into a mod_perl application. the necessary configuration changes
related to mod_perl have been made. however we are facing a no. of problems.
some of the typical problems are:
1) We are a group of three
Andrei A. Voropaev wrote:
Hi!
In the code for DBD::Oracle::db::ping method there are lines
local $SIG{__DIE__};
local $SIG{__WARN__};
As I understand these lines don't do anything though I guess they are supposed
to suppress warning messages and possibly 'die' messages.
George Francis wrote:
Hello,
I have a mod_cgi application, which we are currently in the process of
converting into a mod_perl application. the necessary configuration changes
related to mod_perl have been made. however we are facing a no. of problems.
some of the typical problems are:
Matt Sergeant wrote:
I have an error on my server that I think is caused by an infinite loop in
perl code [*]. Does anyone have a reliable way to detect where this is
happening on a server with lots of code?
http://perl.apache.org/guide/debug.html#Using_the_Perl_Trace
--
Matt Sergeant asked:
I have an error on my server that I think is caused by an infinite loop in
perl code [*]. Does anyone have a reliable way to detect where this is
happening on a server with lots of code?
$SIG{ALRM} = sub {
Carp::confess(Got Apache::Event ALRM);
};
Greetings.
[...]
This documentation patch addresses the single thread snafu on Win32.
Comments, corrections and additions (even subtractions)
welcome. (Also on the hot topic of the day: where in the doc does this
fit?)
Nice, but please repost it inlined. Otherwise people won't be able to
Title: How to create a browser popup window
Hello all,
Can anybody give me the golden tip of creating a popup browser window
from my mod_perl handler? I want to fill in this popup window with results
generated within my handler.
Is there a module available from CPAN which can handle
Title: How to create a browser popup window
how do I unsubscribe from this list.
- Original Message -
From:
Domien Bakker
To: [EMAIL PROTECTED]
Sent: Tuesday, November 20, 2001 6:30
AM
Subject: How to create a browser popup
window
Hello all,
Can anybody
This is not really a mod_perl question. Pop-up windows can only be created
using client-side scripting like Javascript. Your handler would need to
output the necessary Javascript to cause the pop, like:
script
url = /pop/source.html;
name = popwin;
h = 250;
w = 350;
var
How can you specify a Location for these
paramters, or can they be used only from within the current
section?
Issac
Internet is a wonderful mechanism for making a fool
ofyourself in front of a very large audience.
--Anonymous
Moving the mouse won't get you into
trouble... Clicking it
How can you specify a Location for these paramters,
or can they be used only from within the current section?
$r is a request object, so modifications only affect the current request.
If you want to affect all requests, you need to do it in the configuration
stage.
- Perrin
set_handlers() and push_handlers() apply to the current
request (except for the PerlRestartHandler and other handlers that are not
request-oriented). it really doesn't make sense to have them apply only to
a Location or otherwise - if you want them to apply only to a certain
location use
The following message is a courtesy copy of an article
that has been posted to comp.lang.perl.modules,comp.lang.perl.announce as well.
The uploaded file
HTTP-WebTest-1.07.tar.gz
has entered CPAN as
file: $CPAN/authors/id/I/IL/ILYAM/HTTP-WebTest-1.07.tar.gz
size: 61156 bytes
md5:
Off topic but in the interests of, if not less popup windows, then at
least less broken ones:
You must include code to deal with the fact that you may have already
opened a popup window. Something like this:
SCRIPT LANGUAGE=JavaScript
!-- Hide
var popupwin = null;
On Mon, 19 Nov 2001, Ian @ International Sports Agnecy wrote:
if you telnet to port 80 and issue a head request manually, what does the
server report exactly? it should list the modules you have properly
installed.
gedanken
I'm having a bit of a problem getting everything to work right.
You must include code to deal with the fact that you may have already
opened a popup window. Something like this:
That is simply not true. window.open() with a named window ('popupwin', in
your example) ALWAYS reuses that window, on every browser I've ever been
able to test. The second call
Hello,
I hate to keep banging this old drum, but since I was able to reproduce this problem
(but not solve it), I figured I'd recycle it again. Perrin said earlier that this was
fixed in 1.26, but I am indeed using 1.26 and the problem persists. Stas suggested
upgrading perl to 5.6.1 -- I
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 necessary
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 effect.)
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
On Tue, 20 Nov 2001, Alessandro Forghieri wrote:
Greetings.
[...]
This documentation patch addresses the single thread snafu on Win32.
Comments, corrections and additions (even subtractions)
welcome. (Also on the hot topic of the day: where in the doc does this
fit?)
Nice, but
I need mod_perl to not send the Content-type header when a program is
run. Despite the Off value of the PerlSendHeader variable in
httpd.conf, the header is still being sent.
This test program still sends an extraneous Content-type header:
print Content-type: text/html\n\n;
print h1Hello
On Tue, 20 Nov 2001, Rob Bloodgood wrote:
You must include code to deal with the fact that you may have already
opened a popup window. Something like this:
That is simply not true. window.open() with a named window ('popupwin', in
your example) ALWAYS reuses that window, on every
Thanks, Tom. Yep, this does the job just fine and allows me to send
the Content-type later:
print HTTP/1.1 OK\n;
Is ignoring PerlSendHeader considered a feature? ;)
-gm
On Tue, 20 Nov 2001, Tom Mornini wrote:
This took me a LONG time to deal with when I was new to mod_perl...
Hey,
Apache::ASP v2.29 has been released, CHANGES below, and you can
get it in your local CPAN, or:
http://www.perl.com/CPAN-local/modules/by-module/Apache/
There are some major bugs fixed in this release, that stem
from new work in the 2.25 release. These bugs are about empty
$Sessions
The URL
ftp://ftp.dev.ecos.de/pub/perl/session/Apache-SessionX-2.00b3.tar.gz
has entered CPAN as
file: $CPAN/authors/id/G/GR/GRICHTER/Apache-SessionX-2.00b3.tar.gz
size: 11701 bytes
md5: c3998900a065c1f7a87c40bcf6169ef1
Apache::SessionX extents Apache::Session. It was initialy
The URL
ftp://ftp.dev.ecos.de/pub/perl/embperl/HTML-Embperl-2.0b4.tar.gz
has entered CPAN as
file: $CPAN/authors/id/G/GR/GRICHTER/HTML-Embperl-2.0b4.tar.gz
size: 507965 bytes
md5: 03f8ca074b7588fa11ecb8002d4b50bd
Main new feature since 2.0b3 is the beginning support for XML, namely
dougm 01/11/20 18:13:00
Modified:lib/ModPerl BuildOptions.pm
Log:
add missing LIBNAME option to the table
Revision ChangesPath
1.12 +1 -0 modperl-2.0/lib/ModPerl/BuildOptions.pm
Index: BuildOptions.pm
stas01/11/20 18:35:33
Modified:lib/Apache Build.pm
Log:
- add the rebuild() function that allows to reuse the build opts to build
a new mod_perl
Revision ChangesPath
1.73 +26 -0 modperl-2.0/lib/Apache/Build.pm
Index: Build.pm
stas01/11/20 18:39:45
Modified:.Makefile.PL
Log:
s/generate_xs/xs_generate/ to be consistent with make target and
build/xs_generate.pl
Revision ChangesPath
1.54 +2 -2 modperl-2.0/Makefile.PL
Index: Makefile.PL
36 matches
Mail list logo
