Hello Ralf,
I got the following problems, partly by configuration mistake
(on that other machine, where I did have the problems with another
compiled apache and mod_perl, but no longer have this kind of),
and detected the following:
- If the SSLLog path/directory does not exist, there's no error message
within the error_log, and the parent dies with exit(1).
I just greped through the source but didn't see the
error within ssl_log_open(). Maybe the error is detected at some
other point with the source.
- obsolete options are also reported, if marked as or even written
within a comment, e.g.:
[Thu Nov 5 09:44:13 1998] [warn] mod_ssl: Obsolete/unsupported
directive: # Test mark and for option noSSLFakeBasicAuth
[Thu Nov 5 09:42:16 1998] [warn] mod_ssl: Obsolete/unsupported
directive: #noSSLFakeBasicAuth
- CHANGES mailed to the list within 2.0.14 and 2.1b* are not included
within CHANGES file in the distribution.
(would be helpfull for changing old configuration files to newer ones)
- one the machine mentioned above the Server now starts up fine,
and also mod_perl runs without problems but only on insecure
connections.
At secure connections I receive an SIGSEGV on the child also
at URL's, where handlers of mod_perl aren't configured at all.
Without mod_perl the server runs fine, so I assume that's an other
problem with DSO support within mod_perl and not mod_ssl.
I'll try to compile/link with -g and report later on this.
Jan
______________________________________________________________________
Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/
Official Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
