> -----Original Message-----
[]
>
> > Just one thing though. If I 'close STDERR' is this going
> to stop any further
> > Apache messages going to the error log, or does this only
> last for the
> > <perl></perl> context and doesn't affect the Apache
> process's STDERR?
>
> I believe that if you close STDERR after opening it like I suggested,
> that you will just close that STDERR redirect, but STDERR will
> begin to function again as normal. Don't take my word for it though,
> try it and see.
>
Just tested with some debug output and it works. Cheers. I thought it hadn't
at first until I realised I was looking a the wrong log file.
If it hadn't worked it appears you can save STDERR before redirecting by
doing...
open(SAVERR, ">&STDERR");
and restore with...
open(STDERR, ">&SAVERR);
close(SAVERR);
I was about to try that but don't need it now. Useful to know though.
One further question. Currently the scripts include some .pm files by doing
a 'use' statement. Would these perl modules get compiled too or should I be
doing something along the lines on this?...
<Perl>
use lib 'path-to-my-lib';
</Perl>
PerlModule MyLib
I still seem to have to do the 'use' if I do this, so is this gaining me
anything or are the perl modules being compiled anyway just by placing 'use'
in a script that gets precompiled?
Thanks.
Tim.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
