Re: http responses piped to STDERR

Michael Pohl wrote: I'm (very) occasionally seeing the output of Apache::Registry scripts sent to STDERR instead of STDOUT. That is, the entire http response (headers included) appears in my error log, while nothing at all is displayed to the client. Could someone kick me towards what I should

http responses piped to STDERR

I'm (very) occasionally seeing the output of Apache::Registry scripts sent to STDERR instead of STDOUT. That is, the entire http response (headers included) appears in my error log, while nothing at all is displayed to the client. Could someone kick me towards what I should look into here

Re: Win32: Apache2+modperl2 STDERR not going to error.log?

Alessandro Forghieri wrote: Greetings. I am using the binary distribution Apache/2.0.40-dev (Win32) mod_perl/1.99_05-dev Perl/v5.8.0 from uwinnipeg. OS is NTsp6 httpd.conf is basically unmodified. I have noticed that carp'ing or warn'ing or even printing to stderr from a Registry

Try to tie STDERR

Hi, sorry for my offtopic posting but i haven't found a general perl mailinglist (with some traffic). i want to spy my mod_perl/batch programs, in some case they write an error to STDERR i want to send an email to me. So i wrote Log.pm which has tie functions for handlers, but this doesnt

Re: Try to tie STDERR

Bartlomiej Frackiewicz wrote: Hi, sorry for my offtopic posting but i haven't found a general perl mailinglist (with some traffic). i want to spy my mod_perl/batch programs, in some case they write an error to STDERR i want to send an email to me. So i wrote Log.pm which has tie

Re: Try to tie STDERR - Thanks

PROTECTED] Betreff: Re: Try to tie STDERR try taking a look at recipes 6.10 and 16.6 in the mod_perl developer's cookbook - 6.10 ties STDERR just as you do. 16.6 is available online and explainswhy just tie()ing STDERR doesn't capture all possible sources of writes to the error_log.

Re: STDERR

, December 08, 2000 05:46:13 PM -0500 Aleksandr Vladimirskiy [EMAIL PROTECTED] wrote: I am sorry, its just my question wasn't on how to do it ("dup STDERR to STDOUT"), but rather why doing that doesn't work. I have two pieces to the puzzle an apache module and an external script. I get

Re: STDERR

[EMAIL PROTECTED] wrote: I am sorry, its just my question wasn't on how to do it ("dup STDERR to STDOUT"), but rather why doing that doesn't work. I have two pieces to the puzzle an apache module and an external script. I get the errors from the external script in the error_log, so I red

STDERR

Hi, I am writing a module that launches a perl script. I would like the user to see the error cenerated by the script in the browser. So far I either get the errors sent to the apache error_log or the browser respons that the document contained no data. Please help! Alex

RE: STDERR

dup STDOUT to STDERR -Original Message- From: Aleksandr Vladimirskiy [mailto:[EMAIL PROTECTED]] Sent: Friday, December 08, 2000 5:16 PM To: [EMAIL PROTECTED] Subject: STDERR Hi, I am writing a module that launches a perl script. I would like the user to see the error cenerated

Re: STDERR

That would have the opposite effect of what I want. I want the errors to go to the browser not the output of the script to the error_log. ??? Alex Jerrad Pierce wrote: dup STDOUT to STDERR -Original Message- From: Aleksandr Vladimirskiy [mailto:[EMAIL PROTECTED]] Sent: Friday

Re: STDERR

I am sorry, its just my question wasn't on how to do it ("dup STDERR to STDOUT"), but rather why doing that doesn't work. I have two pieces to the puzzle an apache module and an external script. I get the errors from the external script in the error_log, so I redirect them in

Re: STDERR

On Fri, 8 Dec 2000, Aleksandr Vladimirskiy wrote: I am sorry, its just my question wasn't on how to do it ("dup STDERR to STDOUT"), but rather why doing that doesn't work. I have two pieces to the puzzle an apache module and an external script. I get the errors from the exter

RE: STDERR

here's my variation on your question (sorry, not much help to you): while you are in a handler and you catch an error, why can't you then $r-print the error message, and return OK immediately? Perl just dies and Apache returns the header when I try this. Doug | From: [EMAIL PROTECTED]

STDERR

Well I looked at the link on perl.apache.org (http://perl.apache.org/guide/porting.html#STDIN_STDOUT_and_STDERR_streams), and it still isn't working. I must be coding wrong. Please take a look at the code: $r-content_type('text/html'); $r-send_http_header; open (STDERR, "STDOUT");

STDERR

Hey I got it. The code was wrong. So now I do an "open (STDERR, "STDOUT");" in the beginning of the external script and a "tie *OUT, 'Apache';" in the module, then I used backtick to execute so now it dumps everything to browse

Re: STDERR

'); $r-send_http_header; open (STDERR, "STDOUT"); tie *OUT, 'Apache'; $r-print("htmlbody"); $status = system("some.prog.pl", $params{'...'}, $params{'...'}); $r-print("/body/html"); thanks very much Hmm, first OUT filehandler was just an exam

Re: STDERR

On Fri, 8 Dec 2000, Aleksandr Vladimirskiy wrote: Hey I got it. The code was wrong. So now I do an "open (STDERR, "STDOUT");" in the beginning of the external script and a "tie *OUT, 'Apache';" in the module, then I used backtick to execute so now it dumps every