Philip M. Gollucci wrote:
> Jason Rhinelander wrote:
>> Is it, then, intentional?
> You know, I'm not entirely sure, but I betting its because
> STDIN, STDERR, STDOUT are re-tied to the streams in the request object
> automagically for you in Registery/PerlRun under the
efore STDOUT, etc. are tied),
instead of each time the handler runs.
--
-- Jason Rhinelander
documented somewhere.
> Feel free to supply a documentation patch and it will get added.
>
Is it, then, intentional?
--
-- Jason Rhinelander
ional, but in that case it
should at least be documented somewhere.
> It might be considered annoying that Perl doesn't complain if you pass a
> not-yet-defined file handle (stdin in this case). Even with 'use
> strict'.
>
> Regards
> -- tomás
--
-- Jason Rhinelander
Changing the binmode from:
binmode stdout, ":utf8";
to:
binmode STDOUT, ":utf8";
makes it work properly. This seems to me like a bug, but perhaps
someone more familiar with mod_perl's STDOUT tying than I can explain
this (or confirm this as a bug).
--
-- Jason Rhinelander
To ask in a slightly different way: should this behaviour be considered
a bug?
Jason Rhinelander wrote:
Oops, I forgot the URL's:
http://jagerman.com/env.cgi
http://jagerman.com/perl/env.cgi
Jason Rhinelander wrote:
Hi,
I'm seeing some odd behaviour under mod_perl (sp
Oops, I forgot the URL's:
http://jagerman.com/env.cgi
http://jagerman.com/perl/env.cgi
Jason Rhinelander wrote:
Hi,
I'm seeing some odd behaviour under mod_perl (specifically,
ModPerl::Registry - though the problem may be broader than that) with
regards to the effective group ID
doesn't change when
I make changes to the script or restart the server. I also changed the
script to use POSIX::getegid() to see if it was something to do with $),
but it also returns the strange value.
Does anyone have any insight into this?
--
-- Jason Rhinelander
