Hi,
UID 0 based processes? Perhaps then you have to run it on ports 8080/8443
temporarily as a regular user to get the core. Without the coredump and a
backtrace it's hard to find the location of the SIGSEGV.
Thanks for the hint, Ralf.
Meanwhile I got some closer and got at least a
itsel=
f
with perl-5.005_02; everything is fine with perl-5.004_04, but with =
a freshly installed perl-5.005_02 it core-dumps.)
Greetings,
Jan
Mit freundlichen Grüßen / best regards,
UUNET Deutschland GmbH
Jan Wedekind
Manager Techn. Op. Web/Services UUNET
Wait! On _ALL_ my testings on en1.engelschall.com I use port 8080 for HTTP an
d
8443 for HTTPS because en1 also runs the non-testing Apache+mod_ssl on 80/443
.
Well, now I got the message and may explain the behaviour
(which I tried before)
I (and also the other writer to the list) made the
Sorry for german stuff on this list;
mail should go directly to Ralf.
__
Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/
Official Support Mailing List [EMAIL PROTECTED]
Automated List
Hello,
I just tried to compile a SSL-patched (mod_ssl-2.0.13) apache version,
but *without* activating mod_ssl:
gcc -c -I../../os/unix -I../../include -DSOLARIS2=251 -DMOD_PERL
- -DUSE_HSREGEX -DSERVER_SUBVERSION=\"PHP/3.0.3\" -O2 -DFPX_CORE_PATCH
- -I/usr/local/include `../../apaci`
Hello again,
There are also missing some conditional Makerules, to prevent
to make the certificate stuff, if mod_ssl is disabled.
Hm `make certificate' needs to know SSL_BASE and other stuff. This is
only calculated when mod_ssl is actually enabled. So there is no chance to ru
n
Hello Victor,
as the cited begger for DSO I might argue at this:
Hm.
1. Why you need two httpd servers in first place ?
Because to avoid heavy memory consumption for all customer servers.
2. How much is memory penalty for not-used mod_ssl ?
That's not the point; If you want to be
