>
> Try adding "warn $msg" statements (instead of printing to a file).
>
> Perl's "warn" function prints to STDERR, which is usually appended to the web
> server's errors log. To read the errors as they are printed, do the
> following (provided you have shell access on your server, and it's r
> "Perrin" == Perrin Harkins <[EMAIL PROTECTED]> writes:
> On Wed, Aug 20, 2008 at 5:42 PM, Brett Randall <[EMAIL PROTECTED]> wrote:
>> I was wondering about debugging... I'll probably do the good old open
>> a file, write to it after each line, and see where it stops writing
> No need to ope
--- On Wed, 8/20/08, Brett Randall <[EMAIL PROTECTED]> wrote:
> From: Brett Randall <[EMAIL PROTECTED]>
> Subject: Re: Unable to get PerlAuthenHandler to work in mp2
> To: "Perrin Harkins" <[EMAIL PROTECTED]>
> Cc: modperl@perl.apache.org
> Date: Wednesday, August 20, 2008, 3:42 PM
> > "Per
On Wed, Aug 20, 2008 at 5:42 PM, Brett Randall <[EMAIL PROTECTED]> wrote:
> I was wondering about debugging... I'll probably do the good old open a
> file, write to it after each line, and see where it stops writing
No need to open a file. Anything you print to STDERR goes to apache's
error_log,
> "Perrin" == Perrin Harkins <[EMAIL PROTECTED]> writes:
> On Wed, Aug 20, 2008 at 3:03 AM, Brett Randall <[EMAIL PROTECTED]> wrote:
>> I'm trying to get PerlAuthenHandler to work but when I go to a URL
>> that I've set it up on, it asks for a username and password and then
>> lets me in no ma
I use IPC::Run3 quite a bit, and it's a good option for retrieving STDIN
and STDOUT from a forked process.
Be aware that with mod_perl2, subprocesses which are forked using system
and backticks (IPC::Run3 uses system) DO NOT INHERIT THE ENVIRONMENT OF
THE PROCESS FROM WHICH THEY ARE FORKED.
You c
On Wed, Aug 20, 2008 at 3:03 AM, Brett Randall <[EMAIL PROTECTED]> wrote:
> I'm trying to get PerlAuthenHandler to work but when I go to a URL that
> I've set it up on, it asks for a username and password and then lets me
> in no matter what I type.
Have you debugged this code to figure out which
On Wed, Aug 20, 2008 at 11:26 AM, Niels Larsen <[EMAIL PROTECTED]> wrote:
> I can put
> the command line to run in backticks and do print [EMAIL PROTECTED], and
> that too works, but would like to use system, Proc::SafeExec, etc.
To fork and capture output without backticks, you have to do somethi
The system call forks a process and that process inherits the STDOUT
from perl. So since your perl is the persistent interpreter in Apache,
it would make sense that that's where most of the STDOUT messages will go.
I'm not sure if there is a way to intercept the STDOUT of the forked
process in
Greetings,
I have moved a big collection of modules to mod_perl2 under PerlRun
and can see a great speedup, as hoped. But in some of these modules
programs are run that write something to STDOUT that is then captured
and processed - which doesnt work since STDOUT is tie'ed to Apache.
I saw sugges
Thanks Andre and Tyler.
Believe it or not I never even thought of that until you guys pointed it out
(that the hash would live for the the life of the apache child). I can be such
a fool sometimes :)
In this case I assume %cache is global - it only appers in that sub, there is
no "my %cache
W. Tyler Gee wrote:
On Tue, Aug 19, 2008 at 5:35 PM, Chris Faust <[EMAIL PROTECTED]> wrote:
Hi,
This might be a little off topic, I hope it's OK to post. I'm not positive
if mod_perl matters or not because it's a little confusing to me.
I've taken over some pretty old code that I'm updatin
Hey all
I'm trying to get PerlAuthenHandler to work but when I go to a URL that
I've set it up on, it asks for a username and password and then lets me
in no matter what I type.
My entry in Apache's .conf file is:
PerlM
13 matches
Mail list logo
