On Fri, Mar 23, 2001, [EMAIL PROTECTED] wrote:
> Full_Name: Tony Leneis
> Version: mod_ssl-2.8.1-1.3.19
> OS: Tru64 Unix 5.1
> Submission from: (NULL) (139.126.32.100)
>
> mod_ssl doesn't enable semaphore support under Tru64 Unix for the
> SSLMutex configuration directive. Tru64 Unix (and Digital Unix)
> adheres to the single unix specification and POSIX, so unless there's
> a bug I'm not aware of I think it should be compiled in. The cc(1)
> man page for Tru64 Unix 5.1 states the following will uniquely
> identify Tru64 Unix:
>
> #if defined (__digital__) && defined (__unix__)
>
> Unfortunately, this only seems to apply to the 5.x versions. Earlier
> versions (4.0A through 4.0G) define __unix__, __osf__, and __alpha__,
> but not __digital__. Anyway, I changed line 294 in pkg.sslmod/mod_ssl.h (above
> where SSL_CAN_USE_SEM is defined) from
>
> defined(SOLARIS2) || defined(__hpux)
>
> to
>
> defined(SOLARIS2) || defined(__hpux) || \
> (defined (__digital__) && defined (__unix__))
>
> It compiled without any new warnings or errors, and I can see the
> semephore it created with ipcs, so I assume all is well. Can this
> change be rolled into the source tree? Support for the 4.0 releases
> of Tru64 and Digital Unix can probably be added by checking if both
> __osf__ and __alpha__ are defined (though I don't know if you'll
> also get false positives for alphas running Linux.)
Comitted to CVS for mod_ssl 2.8.2.
Thanks for your feedback.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
