On Thu, 28 Sep 2000, Vsevolod Ilyushchenko wrote:
> Hi,
>
> Why does this script give no output under mod_perl, but works fine from the command
>line:
>
> #!/usr/bin/perl -w
>
> use CGI;
>
> print CGI->header();
>
> open (AAA, ">-");
because the C level stdout is not hooked up to the clien
> > Why does this script give no output under mod_perl, but works fine from the
>command line:
> >
> > #!/usr/bin/perl -w
> >
> > use CGI;
> >
> > print CGI->header();
> >
> > open (AAA, ">-");
>
> because the C level stdout is not hooked up to the client. you can do
> this as an alternative:
>
o: Doug MacEachern
>Cc: [EMAIL PROTECTED]
>Subject: Re: open ">-" does not work
>
>
>> > Why does this script give no output under mod_perl, but
>works fine from the command line:
>> >
>> > #!/usr/bin/perl -w
>> >
>> > use CGI;
Jerrad Pierce wrote:
>
> No... that opens a handle to ehir INPUT
>
> output is
> open(OUT, "magic_open |");
I am not sure why, but the command line Perl script with
open (AAA, "|some_program");
accepts input via "print AAA" AND prints the output of the program on stdout.
> Or you c
On Fri, 29 Sep 2000, Vsevolod Ilyushchenko wrote:
>
> I am not sure why, but the command line Perl script with
>
> open (AAA, "|some_program");
>
> accepts input via "print AAA" AND prints the output of the program on stdout.
because C-level stdout is not hooked up to the client under m
On Sep 29, Doug MacEachern wrote:
> On Fri, 29 Sep 2000, Vsevolod Ilyushchenko wrote:
> > Yes, I know. I just want to see how far I can go with the "open".
> > Besides, according to the author of the script (it's for the analog web
> > log analyzer), using open is more secure.
>
> i've never hear
