On 24.10.2008 15:03 Michael Peters wrote:
> This is only true if those structures were created during run time and go out
> of scope at run time.
> If they are generated at compile time or attached to global variables or
> package level variables,
> they will not be re-used by Perl.
Wait a mi
Sergey Kochkarev wrote:
Hi,
I'm new to mod_perl and I got the following problem:
apparently not just to mod_perl..
1. system() outputs to browser. How can I turn this off?
Well, yes.
Anything basically that your script or module prints to STDOUT, will end
up "in the browser". That's the n
Hi,
I'm new to mod_perl and I got the following problem:
1. system() outputs to browser. How can I turn this off?
2. `` works in parallel with perl script, but I want it to finish to
check the files it creates. How can I synchronize `` and perl?
I've googled the sfio term that seems to be the
On Fri, Oct 24, 2008 at 8:57 AM, Carl Johnstone
<[EMAIL PROTECTED]> wrote:
> If you're really concerned and would rather the child process quits and
> frees additional memory to the OS, then call $r->child_terminate in any of
> your handlers, and the child process will automatically quit at the end
Carl Johnstone wrote:
Something else I will do for my low-usage but "massive" scripts (those
that have large memory structures and take several seconds to execute)
is to place these in a non-mod_perl directory so I can be assured their
memory usage goes away at the end of the response.
I was referring to script initialization (responding to that first request)
and not the httpd daemon startup. Really, the only "startup" that should be
slower is when the whole httpd service is restarted (such as at server
startup) since it would have to preload all modules for all standby da
