> 7:15 Apache configuration demonstration
Could we add a little compilation exercise afterwards ?
Motivation: Some of the error messages in mod_ssl are not informative
enough. I would know how to extent the code (ssl_engine_kernel.c) to
improve error logging but experienced problems with dependencies from the
http* tree (headers, libraries,...).
My approach is to do this in some development directory and then only move
the module to /usr/lib/apache/libssl.so
This is a production server, and I can't just run a full make/install and
wait to see what breaks -- again, the idea is to only toggle the old and
new libssl.so (plus httpd restart) to test my changes.
Reasonable approach ?
Anybody up for this tonight ? .................. Horst
source: mod_ssl-2.8.10-1.3.26.tar.gz
apache_1.3.26.tar.gz
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
On Wed, 18 Sep 2002, Larry Price wrote:
> start 6:30pm
> Gather around conference table
> 7:00 futz with ancient hp hub so we can all plug for ethernet
> 7:15 Apache configuration demonstration
> 8:03 laugh when <mumble> drops soda on their kbd
> 8:35 first mention of /.
> 8:53 acceptance of Tux
>
> post meeting bofh lart-o-matic as you stumble over the cruft in the street
> out front
...etc...
_______________________________________________
Eug-lug mailing list
[EMAIL PROTECTED]
http://mailman.efn.org/cgi-bin/listinfo/eug-lug
