On 5/26/05, Perrin Harkins <[EMAIL PROTECTED]> wrote:
> On Thu, 2005-05-26 at 14:53 -0400, Erik Aronesty wrote:
> > ppcgid kicks it's butt in that arena.
>
> > My business partner and I decided on two tactics: he started building a
> > patch to thttpd to run perl scripts natively as opposed to exe
Thanks for the good idea... it is a direction worth investigating
further. Until someone offers a potentially better solution, I will play
around with this and hopefully in the next few days report back on my
results!
Thanks again,
Daniel
Jonathan Vanasco wrote:
I really have no idea, but n
I really have no idea, but no one has chimed up on this, so I'll try to
help (and maybe someone here can clear up my misconceptions)
MP writes to STDERR, BUT things can get weird because of the way
apache2 handles error messages --
I could have this wrong, but mp errors and perl errors seem
On Tue, 2005-05-31 at 12:10 -0700, Kent, Mr. John (Contractor) wrote:
> [Tue May 31 12:06:54 2005] [error] Global $r object is not available.
> Set:\n\tPerlOptions +GlobalRequest\nin httpd.conf
> at /users/webuser/perl/lib/5.8.6/CGI.pm line 348.\n
What happens when you follow those instructions an
Greetings,
Trying to run the CGI.pm 3.10 with the latest Apache and mod-perl
[Tue May 31 11:57:54 2005] [notice] SIGHUP received. Attempting to restart
[Tue May 31 11:57:55 2005] [notice] Apache/2.0.54 (Unix) mod_perl/2.0.0
Perl/v5.8.6 configured -- resuming normal operations
Get the following
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:
On Tuesday 31 May 2005 06:23, Foo Ji-Haw wrote:
> If I am not mistaken, modperl tends to cache all output until the script
> is completed, then it sends out the page. If I want to (for example)
> print a period (.) back to the browser every second, what do I need to
> do? I tried $| but it does not
As more of a hack than a necessarily good practice, I've found that
sending a newline (in addition to $|=1) sometimes helps. I think the
problem here is more that the browser doesn't necessarily render content
every single time some data comes in over the socket, but maybe waits
for logical lookin
Hello Rodger,
Thanks for the advice. I'm concerned that this sounds like a lot of
search-and-replace for my application. I wonder if there is a cleaner
method that simply toggles off buffering?
Anyone has any ideas on this?
Rodger Castle wrote:
If I am not mistaken, modperl tends to cache a
