You are viewing a plain text version of this content. The canonical link for it is here.
Posted to modperl@perl.apache.org by Doug MacEachern <do...@covalent.net> on 2000/04/01 00:31:01 UTC

RE: Segmentation Fault: RedHat 6.[01] / Apache 1.3.12 / mod_perl 1.22 / perl 5.005_03 / IE 5

On Fri, 31 Mar 2000, Vivek Khera wrote:

> >>>>> "GY" == Geoffrey Young <gy...@laserlink.net> writes:
> 
> GY> PerlFreshRestart causes a great many problems, most for indeterminate
> GY> reasons, but its behavior is at least documented
> 
> I'm curious, now with the new code in 1.22 that dl_unloads all of the
> perl XS modules and with the perl shared object also being unloaded,
> doesn't PerlFreshStart cause a whole new perl interpreter to be
> instantiated?  I haven't investigated this but it seems to make
> sense.  Has anyone looked into this?

mod_perl dso will do a full tear-down (perl_destruct()), regardless of
PerlFreshRestart (which still behaves the same old way)


RE: Segmentation Fault: RedHat 6.[01] / Apache 1.3.12 / mod_perl 1.22 / perl 5.005_03 / IE 5

Posted by Vivek Khera <kh...@kciLink.com>.
>>>>> "DM" == Doug MacEachern <do...@covalent.net> writes:

DM> On Mon, 3 Apr 2000, Vivek Khera wrote:
>> What if someone sets PerlFreshRestart No and has DSO enabled?  Then
>> they don't get what they think they do.

DM> right, the docs should be updated to reflect that.

Why not disable this command similarly to how the SSI command is disabled
when we go DSO?




RE: Segmentation Fault: RedHat 6.[01] / Apache 1.3.12 / mod_perl 1.22 / perl 5.005_03 / IE 5

Posted by Doug MacEachern <do...@covalent.net>.
On Mon, 3 Apr 2000, Vivek Khera wrote:
 
> What if someone sets PerlFreshRestart No and has DSO enabled?  Then
> they don't get what they think they do.

right, the docs should be updated to reflect that.



RE: Segmentation Fault: RedHat 6.[01] / Apache 1.3.12 / mod_perl 1.22 / perl 5.005_03 / IE 5

Posted by Vivek Khera <kh...@kciLink.com>.
>>>>> "DM" == Doug MacEachern <do...@covalent.net> writes:

>> If so, then it should be an error or warning to specify it when using DSO.

DM> well, it's still a FreshRestart, just fresher than static-modperl :)

What if someone sets PerlFreshRestart No and has DSO enabled?  Then
they don't get what they think they do.

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Vivek Khera, Ph.D.                Khera Communications, Inc.
Internet: khera@kciLink.com       Rockville, MD       +1-301-545-6996
PGP & MIME spoken here            http://www.kciLink.com/home/khera/

RE: Segmentation Fault: RedHat 6.[01] / Apache 1.3.12 / mod_perl 1.22 / perl 5.005_03 / IE 5

Posted by Doug MacEachern <do...@covalent.net>.
On Fri, 31 Mar 2000, Vivek Khera wrote:

> >>>>> "DM" == Doug MacEachern <do...@covalent.net> writes:
> 
> DM> mod_perl dso will do a full tear-down (perl_destruct()), regardless of
> DM> PerlFreshRestart (which still behaves the same old way)
> 
> Implying that PerlFreshRestart is ignored when mod_perl is DSO.
> Correct?

right.

>  If so, then it should be an error or warning to specify it when using DSO.

well, it's still a FreshRestart, just fresher than static-modperl :)


RE: Segmentation Fault: RedHat 6.[01] / Apache 1.3.12 / mod_perl 1.22 / perl 5.005_03 / IE 5

Posted by Vivek Khera <kh...@kciLink.com>.
>>>>> "DM" == Doug MacEachern <do...@covalent.net> writes:

DM> mod_perl dso will do a full tear-down (perl_destruct()), regardless of
DM> PerlFreshRestart (which still behaves the same old way)

Implying that PerlFreshRestart is ignored when mod_perl is DSO.
Correct?  If so, then it should be an error or warning to specify it
when using DSO.