> Good guess. mod_ssl adds some initialization code add the end of
> common_init(), and so does lingerd.... which is why lingerd's patch
> wasn't applying cleanly.
>
> I had to make a different patch, for use with mod_ssl. The file is
> ftp://iagora.com/pub/software/lingerd/tmp/aplinger-ssl.diff (I'll
> put it in a proper lingerd release once I've checked a bit more
> closely how it all works)
>
> With this patch, I got Apache to build with lingerd, mod_perl and
> mod_ssl, and it seems to work fine. Netscape can access it, the
> ssl_engine_log doesn't show any errors, and keep-alive works.
>
I'm running Ben's apache_ssl + mod_perl and am considering adding
lingerd to the mix. I already have lingerd + apache running on the
lite-weight end, and wonder if apache_ssl has similar problems BEFORE
I mess up my production server.
Michael
[EMAIL PROTECTED]
