On Wed, Mar 24, 1999 at 08:22:06AM +0100, [EMAIL PROTECTED] wrote:
> On Wed, Mar 24, 1999, [EMAIL PROTECTED] wrote:
>
> > Full_Name: John Hoffmann
> > Version: 2.2.5-1.3.4
> > OS: Solaris 2.6
> > Submission from: stargate.trytel.com (209.167.85.20)
> >
> > I'm trying to switch from StrongHold 2.4 to Apache 1.3.4 with
> > mod_ssl, and I must say the installation went 200 times easier.
> > One thing I am having a problem with however is getting PHP 3 to
> > work at all.
> >
> > I recently compiled StrongHold with mod_auth_mysql-2.20, php 2.01
> > and php 3.0.7 and it worked fine, but when I compile these same
> > modules into Apache 1.3.4 with mod_ssl the php3 engine seems to die.
> > When accessing a .php3 page I simply get a "The document contains no
> > data". PHP 2 pages work fine. I've checked my configuration:
> >
> > srm.conf:AddType application/x-httpd-php3 .php3
> >
> > But no PHP 3 pages will return any data. Any ideas at all?
>
> No, I'm neither using PHP3 myself nor have deep experiences with it, so I
> cannot help you very much. But because this doesn't look like it's really
> mod_ssl related, I recommend you to write to the PHP3 support mailing lists.
>
> Ralf S. Engelschall
> [EMAIL PROTECTED]
> www.engelschall.com
>
The problem turns out to be a limit on the file descriptors that each process
can open, I removed some VirtualHosts and it worked, now to figure out how
to increase the limit on Solaris 2.6 ... anyways, thanks for the quick
response, much faster than the Stronghold Commercial team ;')
--
John Hoffmann <[EMAIL PROTECTED]>
______________________________________________________________________
Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/
Official Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
