OK, I built mod_ssl 2.1.3-1.3.3 exactly the same way on both my
Linux 2.0.35 and my Sun Solaris 2.6 machines. I am running Sybase
on the Sun, by the way (not the Linux release of Sybase). I use the
exact same shell scripts to do the builds on both machines.
If I fire up the mod_ssl version of http on Linux, and enable the ssl
module, I can connect to my Sybase database and display results. I
have a small php3 script to do this.
My test script does not do persistent connections. I disabled that. It
is strictly connect, query, disconnect.
On Solaris, the exact same setup gives me the exit signal Pollable Event (22)
whatever that is.
If on Solaris, I disable the ssl module (apachectl start), the test php script
works fine.
I can also get this Pollable Event error on Solaris if I try to do database
queries via DBI/DBD or via mod_perl's Sybperl module.
If I run an external CGI script (outside of Apache) to do a DB query and
format the results as HTML, of course, it works fine. I only have problems
when I'm working with Apache modules.
Solaris is doing something weird and I don't know how to determine what. Help!
Should I post this to an Apache list?
[Sat Dec 12 12:34:54 1998] [notice] Apache/1.3.3 (Unix) mod_perl/1.16_01
PHP/3.0.5 mod_ssl/2.1.3 SSLeay/0.9.0b configured -- resuming normal operations
[Sat Dec 12 12:35:16 1998] [notice] httpd: child pid 6383 exit signal Pollable Event
(22)
______________________________________________________________________
Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/
Official Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
