Re: File Descriptor used by FileHandle under mod_perl 2.0.4 - is it a perl/mod_perl bug ?

2009-06-30 Thread Scott Gifford
Shibi NS writes: [...] > is my assumption is wrong "FD 0" is reserved for STDIN ? It's partly right: FD 0 is standard input by convention (and also by definition) but it's not reserved or otherwise treated specially by the OS or by Perl. Scott.

Re: File Descriptor used by FileHandle under mod_perl 2.0.4 - is it a perl/mod_perl bug ?

2009-06-30 Thread Shibi NS
This is giving problem to me Before I open this log file I noticed that the FD0 is points a pipe , may be the pipe gets closed when it comes to cleanup_register The problem arises in following scenario 1. This changes my Apache parent process FD 0 to open to this log file. 2. Later the fi

Re: File Descriptor used by FileHandle under mod_perl 2.0.4 - is it a perl/mod_perl bug ?

2009-06-30 Thread Scott Gifford
Shibi NS writes: [...] > my $log = new FileHandle("process.log", "a"); > > When I print the $log->fileno it print FD as 0 and I have couple other log > files opened after this all of these having random numbers like 12,15 etc. my > believe is FD 0 used for STDIN . Is this is bug or aim doing >

File Descriptor used by FileHandle under mod_perl 2.0.4 - is it a perl/mod_perl bug ?

2009-06-30 Thread Shibi NS
Hi All, One of my application is using following code to execute a long running process and the control is return to the user with link to log file so that users can monitor the progress $req->pool->cleanup_register(sub{$self->final_process( $req,$cgi) ;}); And in final_process sub I have Fi

Re: trying to add header field using PerlInputFilterHandler to proxy packets

2009-06-30 Thread William T
On Mon, Jun 29, 2009 at 8:07 PM, Brandon Allgood wrote: > I am running an apache server 2.2.3 on CentOS 5.2. I have turned on the > proxy with the following lines from my apache.conf: > > > ProxyRequests On > > Order deny,allow > Deny from all > Allow from all > > > > I would like

Re: quick pure perl question

2009-06-30 Thread Bill Moseley
On Tue, Jun 30, 2009 at 6:13 AM, André Warnier wrote: > Basically, by using the '>:raw' encoding for the output stream, I was not > expecting perl to warn me that I was (knowingly) outputting "wide > characters" there, so I was surprised at the warning. > > I /would/ have expected it if I was /no

Re: quick pure perl question

2009-06-30 Thread Andy Armstrong
On 30 Jun 2009, at 14:13, André Warnier wrote: I /would/ have expected it if I was /not/ specifying an encoding, like using simply '>'. But not when I am explicitly specifying '>:raw', which in my mind, and according to my interpretation of the on-line documentation, is equivalent to saying

Re: quick pure perl question

2009-06-30 Thread André Warnier
Andy Armstrong wrote: On 28 Jun 2009, at 17:33, Bill Moseley wrote: You need to encode the character data before writing back out either by encoding explicitly or using a layer. Or possibly not decode it in the first place and treat it as an opaque octet stream. All depending, of course, on

Re: quick pure perl question

2009-06-30 Thread Andy Armstrong
On 28 Jun 2009, at 17:33, Bill Moseley wrote: You need to encode the character data before writing back out either by encoding explicitly or using a layer. Or possibly not decode it in the first place and treat it as an opaque octet stream. All depending, of course, on what it is you're tryi

Re: trying to add header field using PerlInputFilterHandler to proxy packets

2009-06-30 Thread Torsten Foertsch
On Tue 30 Jun 2009, Brandon Allgood wrote: > PerlInputFilterHandler company::AddHeader >   > and I wrote the following example handler >   > package company::AddHeader; >   > use strict; > use warnings; >   > use Apache2::Filter (); > use Apache2::RequestRec (); > use APR::Table (); >   > use Apach