I had the same issue on Linux. My build had mod_perl compiled in static
but mod_so was also compiled in. PerlFreshRestart was off, I didn't have
any Perl sections, and no modules were loaded dynamically. My root
process would grow by about 1MB each time it was HUPed. Something about
mod_so
Doug MacEachern wrote:
I have a static Solaris compilation, and have the same problems
where the parent seems to grow by 1M each HUP.
that's strange, do you have PerlFreshRestart On or some Perl sections?
otherwise, kill -HUP with a static modperl is a noop.
You got me! I have Perl
On Fri, Apr 21, 2000 at 11:28:18AM -0700, Joshua Chamas wrote:
Doug MacEachern wrote:
I have a static Solaris compilation, and have the same problems
where the parent seems to grow by 1M each HUP.
that's strange, do you have PerlFreshRestart On or some Perl sections?
otherwise,
You got me! I have Perl sections ... but I didn't know
it was such a crime. Pretty bizarre behavior if you ask me.
it's not a crime, but if you're running Perl code during restart there's a
strong chance you'll be growing the server size. i agree 1M is bizarre
though.
Hi all,
On Thu, 20 Apr 2000, Doug MacEachern wrote:
I have a static Solaris compilation, and have the same problems
where the parent seems to grow by 1M each HUP.
that's strange, do you have PerlFreshRestart On or some Perl sections?
otherwise, kill -HUP with a static modperl is a
