I work with David... and figured you guys might like to see what version's
we're running... (which is already partially explained by the 1.23 comment
below)
(Apache)
Server Version: Stronghold/2.4.2 Apache/1.3.6 C2NetEU/2410 (Unix)
mod_perl/1.21 ApacheJServ/1.0
(Perl)
Summary of my perl5 (5.0 patchlevel 5 subversion 3) configuration:
Platform:
osname=solaris, osvers=2.6, archname=sun4-solaris
uname='sunos 5.6 generic_105181-06 sun4u sparc sunw,ultra-1 '
hint=recommended, useposix=true, d_sigaction=define
usethreads=undef useperlio=undef d_sfio=undef
Compiler:
cc='gcc', optimize='-O', gccversion=2.8.1
cppflags='-I/usr/local/include'
ccflags ='-I/usr/local/include'
stdchar='unsigned char', d_stdstdio=define, usevfork=false
intsize=4, longsize=4, ptrsize=4, doublesize=8
d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=16
alignbytes=8, usemymalloc=y, prototype=define
Linker and Libraries:
ld='gcc', ldflags =' -L/usr/local/lib'
libpth=/usr/local/lib /lib /usr/lib /usr/ccs/lib
libs=-lsocket -lnsl -ldb -ldl -lm -lc -lcrypt
libc=/lib/libc.so, so=so, useshrplib=false, libperl=libperl.a
Dynamic Linking:
dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags=' '
cccdlflags='-fPIC', lddlflags='-G -L/usr/local/lib'
-----Original Message-----
From: Stas Bekman [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 19, 2000 1:07 PM
To: David Veatch
Cc: Geoffrey Young; [EMAIL PROTECTED]
Subject: RE: PerlFreshRestart Question/Problem
> At 01:22 PM 5/19/00 -0400, Geoffrey Young wrote:
> >I think the title says it best:
>
>http://perl.apache.org/guide/troubleshooting.html#Evil_things_might_happen
> _when_us
>
> Sweet. Thanks. So the problem is probably any number of weak module
> issues. That's enough for me right now... turning it off certainly
> fixed it.
Huh? Wasn't the mod_perl 1.23 supposed to fix this problem with DSO? I
thought to remove this item from the Guide. Are there still problems with
DSO?
If I remember correctly the problem was of broken internal pointers when
the DSO code was reloaded.
> >you're killing yourself with StatINC in production.
> >
> >http://perl.apache.org/guide/porting.html#Configuration_Files_Writing_Dy
>
> We really haven't noticed any performance hit... nothing dramatic enough
> to detect anyway. Our database calls are far more expensive than
> checking the modules in %INC so far... and we've optimized our use of
> connections and selects quite a bit. It is certainly a concern that
> we're keeping in mind, though.
Attach to one of the servers with 'strace' and see how many stat calls it
does with StatINC turned on.
_____________________________________________________________________
Stas Bekman JAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide http://perl.apache.org/guide
mailto:[EMAIL PROTECTED] http://perl.org http://stason.org/TULARC
http://singlesheaven.com http://perlmonth.com http://sourcegarden.org
