Return-Path: Delivered-To: apmail-perl-modperl-archive@www.apache.org Received: (qmail 57841 invoked from network); 15 Dec 2006 11:51:56 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 15 Dec 2006 11:51:56 -0000 Received: (qmail 76131 invoked by uid 500); 15 Dec 2006 11:49:43 -0000 Delivered-To: apmail-perl-modperl-archive@perl.apache.org Received: (qmail 74647 invoked by uid 500); 15 Dec 2006 11:49:30 -0000 Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list modperl@perl.apache.org Received: (qmail 72484 invoked by uid 99); 15 Dec 2006 11:49:16 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Dec 2006 03:49:16 -0800 X-ASF-Spam-Status: No, hits=3.9 required=10.0 tests=DNS_FROM_RFC_ABUSE,DNS_FROM_RFC_POST,HTML_MESSAGE X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy includes SPF record at spf.trusted-forwarder.org) Received: from [217.12.10.212] (HELO web26001.mail.ukl.yahoo.com) (217.12.10.212) by apache.org (qpsmtpd/0.29) with SMTP; Fri, 15 Dec 2006 02:49:49 -0800 Received: (qmail 99895 invoked by uid 60001); 15 Dec 2006 10:49:27 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.co.uk; h=X-YMail-OSG:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=xGnlsoNWyPtjD+OfaRKuWZaeDW2CvVqsWjxBGQfvqd5FcLIBLRIaopDzBf5Slr6Fsft8ahpmTiVAuwHtmdTKFmrP7n7taNLTxyZS+08PEoK9u6GQ3bnJ2mTFOTeN2CDhCasBfltgU0AKmh4dh1y/9qNI1blAjV4Osgpat6KP/7Q=; X-YMail-OSG: xi0wd90VM1k_wHRMbKqCuP4tvbveu9MFS4rT098H3J1u1tZrfAQiCSqJ3TNW4kindgLEflv4I3IR1NWfmgEgWc2im9Qiid3D3GnA7RxDYK5AzlhMoIZHQEGfQ4d7LMgsZpP6O9sm5L29 Received: from [161.85.127.139] by web26001.mail.ukl.yahoo.com via HTTP; Fri, 15 Dec 2006 10:49:27 GMT Date: Fri, 15 Dec 2006 10:49:27 +0000 (GMT) From: Anthony Gardner Subject: Re: syswrite + Apache? To: Perrin Harkins , Alex Beamish Cc: mod_perl list In-Reply-To: <45819505.6060308@elem.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-670961199-1166179767=:99707" Content-Transfer-Encoding: 8bit Message-ID: <842180.99707.qm@web26001.mail.ukl.yahoo.com> X-Virus-Checked: Checked by ClamAV on apache.org --0-670961199-1166179767=:99707 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Doh!! Think I've solved it. I used $r instead of Apache2::RequestIO and it works. Plus, I forgot to uniti STDOUT before tie(ing) Now, just gotta try it on the ever reliable RHEL 1.99!!!!! Perrin Harkins wrote: Alex Beamish wrote: > I'm going > to seriously consider looking through the mod_perl docs to see if > there's a way to make sure a reader understands that if they want to do > anything with STDOUT .. that they can't. The tied STDOUT is actually pretty well-documented in my opinion: http://perl.apache.org/docs/2.0/user/config/config.html#C_perl_script_ http://perl.apache.org/docs/1.0/guide/porting.html#STDIN__STDOUT_and_STDERR_streams http://perl.apache.org/docs/2.0/api/Apache2/SubProcess.html#C_spawn_proc_prog_ http://perl.apache.org/docs/2.0/api/Apache2/RequestIO.html There's more here about how this affects forking and system(): http://perl.apache.org/docs/1.0/guide/performance.html#Starting_a_Long_Running_External_Program If there's a place in the docs where you think it would be relevant but it isn't mentioned, you're more than welcome to send in a correction. There are instructions for checking out the docs source on the website. - Perrin --------------------------------- Win tickets to the 2006 FIFA World Cup Germany with Yahoo! Messenger. --0-670961199-1166179767=:99707 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Doh!!

Think I've solved it. I used $r instead of Apache2::RequestIO and it works. Plus, I forgot to uniti STDOUT before tie(ing)

Now, just gotta try it on the ever reliable RHEL 1.99!!!!!



Perrin Harkins <perrin@elem.com> wrote:
Alex Beamish wrote:
> I'm going
> to seriously consider looking through the mod_perl docs to see if
> there's a way to make sure a reader understands that if they want to do
> anything with STDOUT .. that they can't.

The tied STDOUT is actually pretty well-documented in my opinion:
http://perl.apache.org/docs/2.0/user/config/config.html#C_perl_script_
http://perl.apache.org/docs/1.0/guide/porting.html#STDIN__STDOUT_and_STDERR_streams
http://perl.apache.org/docs/2.0/api/Apache2/SubProcess.html#C_spawn_proc_prog_
http://perl.apache.org/docs/2.0/api/Apache2/RequestIO.html

There's more here about how this affects forking and system():
http://perl.apache.org/docs/1.0/guide/performance.html#Starting_a_Long_Running_External_Program

If there's a place in the docs where you think it would be relevant but
it isn't mentioned, you're more than welcome to send in a correction.
There are instructions for checking out the docs source on the website.

- Perrin


Win tickets to the 2006 FIFA World Cup Germany with Yahoo! Messenger. --0-670961199-1166179767=:99707--