On Fri, Apr 23, 1999, Rolf Haberrecker wrote:
> [...]
> > Then welcome to the club of people fighting against SuSE's broken NDBM
> > library... Use --enable-rule=SSL_SDBM as a workaround.
>
> I'd really like to know what's going on here. I couldn't find serious
> problems regarding the session cache when using Apache 1.3.4 or 1.3.6
> from SuSE Linux 6.1
>
> Our init scripts sets the following once Apache has started up:
>[...]
> For some reason the db files seem to get created before Apache changes
> it's UID to wwrun. Changing the ownership of the correspondig files
> after startup makes it work.
That they are created before the UID switch is correct and intended this way
and mod_ssl contains actually a chown(2) call for the database files. So the
explicit chown from the shell shouldn't be needed. Can you find out why the
chown(2) in ssl_engine_scache.c doesn't work for you?
BTW, the reason why SuSE's NDBM especially breaks for mod_ssl can be related
to the fact that mod_ssl writes larger entries to the DB than other programs.
Perhaps it breaks when a limit (e.g. the 1024 bytes) are reached? It should
give an error and that's what mod_ssl expects. But perhaps instead of an error
it segfaults?
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.engelschall.com/sw/mod_ssl/
Official Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
