And lastly before I put this to rest...
> -----Original Message-----
> From: Sam Horrocks [mailto:[EMAIL PROTECTED]
> Sent: Thursday, March 13, 2003 2:16 PM
> To: Dallas Engelken
> Cc: [EMAIL PROTECTED];
> [EMAIL PROTECTED]
> Subject: Re: [Persistentperl-users] Followup to my STDOUT issue
>
>
> > My question to you is, why can I read the STDOUT when I
> use the perl or suidperl interpreter but not perperl.
>
> Because PersistentPerl does not support reading input from
> STDOUT. The
> PersistentPerl code is not written to accomodate that.
>
> The reasons PersistentPerl doesn't support reading from STDOUT are:
>
> 1) It's not trivial to implement in the current way of
> doing things.
>
> 2) An overwhelming majority of the the perl programs out there
> use STDOUT only for output. They do this because, by Unix
> convention, STDOUT is used for output, not input.
>
qmail-queue reads a mail message from descriptor 0. It then reads envelope
information from descriptor 1. It
places the message into the outgoing queue for future delivery by qmail-send.
perl can read descriptor 1, suidperl can read descriptor 1, perperl CANNOT read
descriptor 1.
maybe someone wants to tackle a patch to PersistentPerl to add this capability. I
know it's beyond me since both the perperl frontend and backend are in C.
Dallas
-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open!
Get cracking and register here for some mind boggling fun and
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
_______________________________________________
Qmail-scanner-general mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/qmail-scanner-general