Marcin Kasperski wrote:
PS If only someone had some idea how to solve the DSO/Tru64 problem...
We really need to find people on these platforms (True64, AIX,
HP-UX, etc.) who can help to reproduce and resolve this kind of
probs. If you know of those willing to help please ask them to
subscribe
At 11:41 29.05.2002, Arnold van Kampen wrote:
Hi
Some messages ago, someone still mentioned that modperl had been
- compiled in -,
when describing his configuration, that he was having trouble with.
Does this mean it is still better to compile it in instead of
using mod_perl as a dso?
If
Kampen
Cc: [EMAIL PROTECTED]
Subject: Re: dso
At 11:41 29.05.2002, Arnold van Kampen wrote:
Hi
Some messages ago, someone still mentioned that modperl had been
- compiled in -,
when describing his configuration, that he was having trouble with.
Does this mean it is still better
On Sun, 14 Apr 2002, Sreeji K Das wrote:
Hi Stas,
Thanx for the reply. However, I had already read the
doc. and done everything mentioned there. I had
recompiled perl with -Ubincompat5005 as mentioned.
wondering if this is the XSLoader vs DynaLoader mentioned earlier today.
there is a
Thanx Doug for the reply. Unfortunately I still get
segfaults :-( No difference.
Once I have the time, I'll get the stacktrace see
for any clues. Right now I have kept DSO in the
backburner, as I have got PerlFreshRestart fully up
and runnig (with a no. of patches to mod_perl)
Sreeji
--- Doug
you might actually be hitting a problem i just found on solaris with 2.0
and perl 5.6.1. a problem that is fixed in 5.8.0-tobe, where
certain DynaLoader and XSLoader combo prevents modperl from closing all of
the dlhandles. try adding this to your startup.pl before use-ing any
other
Hi Stas,
Thanx for the reply. However, I had already read the
doc. and done everything mentioned there. I had
recompiled perl with -Ubincompat5005 as mentioned.
I've attached some additional info., generated by
trussing the child, as it was being restarted:
$truss -ef -o ~/truss.out -r0,1,2
Sreeji K Das wrote:
Thanx for the reply. However, I had already read the
doc. and done everything mentioned there. I had
recompiled perl with -Ubincompat5005 as mentioned.
Good then. I just wasn't sure. Hopefully someone with Solaris
access/knowledge will be able to help you out, but see
Sreeji K Das wrote:
Hi,
I was trying to run mod_perl as DSO on Solaris. I see
the following line in the logs:
[notice] child pid 24323 exit signal Segmentation
Fault (11)
This happens whenever I send a USR1 to the server for
restart. Also I see the same message whenever the
child
JC == John Chia [EMAIL PROTECTED] writes:
JC On 27 November 2001 15:17 (-0500), Vivek Khera wrote:
The *only* issue I encounter is a massive memory leak upon SIGHUP or
SIGUSR to apache.
JC Hm. I only get memory leaks if PerlFreshRestart is enabled and I SIGHUP
JC it.
Perl 5.005_03 has the
On Wed, Nov 28, 2001 at 10:34:00AM -0500, Vivek Khera wrote:
SR == Stephen Reppucci [EMAIL PROTECTED] writes:
SR If we're collecting a list of things that don't work in a DSO
SR build, add perl subs (via !--#perl sub=My::handler--).
SR At least, they didn't work as of January of this
SR == Stephen Reppucci [EMAIL PROTECTED] writes:
SR If we're collecting a list of things that don't work in a DSO
SR build, add perl subs (via !--#perl sub=My::handler--).
SR At least, they didn't work as of January of this year.
Doubtful that they ever will, either, since that introduces a
Of Vivek Khera
Sent: Tuesday, November 27, 2001 2:17 PM
To: [EMAIL PROTECTED]
Subject: Re: DSO Issues
DW == David Wheeler [EMAIL PROTECTED] writes:
DW While it seems to be well-known anecdotally that one
should never use a
DW DSO install of mod_perl (particularly among Mason
developers
On 27 November 2001 15:17 (-0500), Vivek Khera wrote:
The *only* issue I encounter is a massive memory leak upon SIGHUP or
SIGUSR to apache.
Hm. I only get memory leaks if PerlFreshRestart is enabled and I SIGHUP
it.
--
john chia [EMAIL PROTECTED] starnix
DW == David Wheeler [EMAIL PROTECTED] writes:
DW While it seems to be well-known anecdotally that one should never use a
DW DSO install of mod_perl (particularly among Mason developers), is there
DW yet any place where all the known issues surrounding the use of DSO
The *only* issue I
If we're collecting a list of things that don't work in a DSO
build, add perl subs (via !--#perl sub=My::handler--).
At least, they didn't work as of January of this year.
On Tue, 27 Nov 2001, John Chia wrote:
On 27 November 2001 15:17 (-0500), Vivek Khera wrote:
The *only* issue I
On Thu, 16 Aug 2001, Stas Bekman wrote:
Currently what I've is:
* How do I build on Solaris with DSO?
= Build perl and mod_perl using the system malloc
that should be any platform where perl defaults to using its own malloc,
that is, if:
% perl -V:usemymalloc
reports:
usemymalloc='y'
On Thu, Aug 16, 2001 at 09:35:43AM -0700, Doug MacEachern wrote:
that should be any platform where perl defaults to using its own malloc,
that is, if:
% perl -V:usemymalloc
reports:
usemymalloc='y'
which is fine if:
% perl -V:bincompat5005
reports:
bincompat5005='undef';
but the
On Thu, 16 Aug 2001, Alex Povolotsky wrote:
This is perl, v5.6.1 built for sun4-solaris
# perl -V:usemymalloc
usemymalloc='n';
that's fine.
Seems like I'm suffering from dying children problem... My main apache
dies sometimes, bringing neraly everything (well, except
server-status)
Oliver [EMAIL PROTECTED] wrote:
Hello,
OK, but I can I govern this:
in the apache configuration of ./configure
I tried to add some DSO (Dynamical Shared Objects) like this
./configure --enable-module=most --enable-shared=max --enable-suexec --suexe
c-caller=apache --suexec-docroot=/home
DM == Doug MacEachern [EMAIL PROTECTED] writes:
DM 1.21_01 had two dso fixes, one to close all .so's opened by DynaLoader and
DM one to call perl_shutdown(), both of which were large leaks. with
DM 1.25_01-dev and Perl 5.6.1 i see a 4k growth on the first kill -USR1 and
DM no change after
On Thu, 14 Jun 2001, Paul G. Weiss wrote:
I know that this is an ongoing problem, but I seem to remember that
someone somewhere had a patch that reduced the size of the memory leak on
restarts to a manageable size. Has this patch been applied to the CVS
version? If not, can some kind soul
All these tips and benchmarks on optimising mod_perl by preloading used
modules/DBD-drivers etc. are great. However, I have seen warnings about
preloading modules if mod_perl is loaded as a DSO. (e.g for
HTML::Embperl). Does this still apply? My setup is
redhat6.2/perl-5.6/mod_perl-1.23.
Hi there,
On Thu, 3 Feb 2000, Wang, Pin-Chieh wrote:
Ged,
Thanks much for your help, Please tell me if I asked too many
questions, If you don't I'll keep on ask you questions. After I
said that, here is another question.
You aren't asking too many questions, but please forgive me if I
"Frank D. Cringle" wrote:
Daniel Jacobowitz [EMAIL PROTECTED] writes:
This worked! Can I get opinions on the attached patch?
I am not competent to check whether the patch has any hidden problems,
but I hope Doug will be able to evaluate it and include it in the next
release. Your
On Fri, Jan 14, 2000 at 06:31:50PM +0200, Stas Bekman wrote:
Just read the mod_ssl vs. apache_ssl thread at /.org:
http://slashdot.org/apache/99/12/22/1711203.shtml
jimjag claims that DSO is slower than static builds at the runtime:
QUOTE
Q: Why has using DSOs anything to do with
26 matches
Mail list logo
