Memory Usage

We are concerned about how much memory we are using now that we are moving to modperl.   Are there any good tools/procedures that we could use to determine how much memory our application is currently using – and then using that as a benchmark, determine how much more or less memory we ar

RE: Receiving user input

00, Daniel B. Hemmerich wrote: > 2. Have that script redirect the user via GET to another script > using a relative path to the same virtual host Are you doing an internal redirect rather than a real redirect? CGI.pm doesn't know how to detect that, since it's an internal apac

RE: Receiving user input

I found that CGI.pm doesn't work quite as I would have expected in our implementation of it. We are temporarily using PerlRun while we re-write some of this code to work efficiently under ModPerl2. Under PerlRun, when taking these steps: 1. Have a form POST to a script 2. Have tha

Receiving user input

Anyone have a code snippet of a routine that will parse both POST and GET user input and place it into a hash?   Thanks!  

RE: Best Practices Question

$return; } $MODIFIED{$file} = -M _;# Update the MODIFICATION times } } -Original Message- From: Michael Peters [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 29, 2006 12:39 PM To: [EMAIL PROTECTED] Cc: modperl@perl.apache.org Subject: Re: Best Practices Question Daniel

Best Practices Question

What is a better route to go?   Have a handler in Apache call a package directly using a handler() – having the module itself parse out arguments passed in and loading configuration files based on argument values. Build a script in /cgi-bin/ that uses mod_perl2, par

Re: Apache Error Log Format

Stas Bekman wrote: Who generates this "Can't locate" message? Normal die() messages should already be prefixed. This is occuring during a require, such as: require '/www/path/goes/here//config.pl'; The script itself is poorly written since it should be doing its own -e check prior to requir

Re: Apache Error Log Format

That sounds more like the opposite... I do want Apache to be prefixing each error message with its data... Unless I misunderstood what that page was saying Arshavir Grigorian wrote: Daniel B. Hemmerich wrote: Thanks for the good idea... it is a direction worth investigating further. Until

Re: Apache Error Log Format

himed up and that tie to STDOUT really popped out in my memories when I read this post. On May 31, 2005, at 8:36 AM, Daniel B. Hemmerich wrote: Hello all... When a misconfiguration occurs, we receive a new line in the apache error logs that is not in the standard error log format (I assum

Apache Error Log Format

Hello all... When a misconfiguration occurs, we receive a new line in the apache error logs that is not in the standard error log format (I assume since MP is writing to STDERR). Short of changing all of our scripts to properly log, is there a quicker method to accomplish the following change: