On Jan 26, Doug MacEachern wrote:
> =item anoncvs
>
> To checkout a fresh copy from anoncvs use
>
> cvs -d "pserver:[EMAIL PROTECTED]:/home/cvspublic" login
>
> with the password "anoncvs".
>
> cvs -d "pserver:[EMAIL PROTECTED]:/home/cvspublic" co modperl
Both of those should have another co
On Wed, 26 Jan 2000, Daniel Jacobowitz wrote:
> Here's a question - an apache patch should be able to mark the module
> as not-to-unload (although since it should be
> not-to-unload-unless-removed-from-config it would be a bit more
> complicated than that - still not impossible). But is that wo
On Wed, Jan 26, 2000 at 08:13:41PM -0800, Doug MacEachern wrote:
> right, that's one of the reasons restarts are a noop for mod_perl by
> default (not including dso-magic)
Makes sense.
Here's a question - an apache patch should be able to mark the module
as not-to-unload (although since it shoul
On Fri, 21 Jan 2000, Daniel Jacobowitz wrote:
> (with appropriate changes to unload DSOs after shutting down perl, of
> course).
>
> I still get memory leakage - that's not terribly surprising - but it is much
> less. It's on the order of about 24K/restart and is probably the fault of
> some mo
> (with appropriate changes to unload DSOs after shutting down perl, of
> course).
>
> I still get memory leakage - that's not terribly surprising - but
> it is much
> less. It's on the order of about 24K/restart and is probably the fault of
> some module - my guts would be DBD::Pg. I'll play ar
(with appropriate changes to unload DSOs after shutting down perl, of
course).
I still get memory leakage - that's not terribly surprising - but it is much
less. It's on the order of about 24K/restart and is probably the fault of
some module - my guts would be DBD::Pg. I'll play around with tha
