"Jared D. McNeill" <jmcneill@invisible.yi.org> writes:
> 
> Although I am having trouble now (I don't know if it's related or not)
> with apache deciding to not start. Ever since I upgraded to php-4.0.4.1
> I've been having this problem. The only way to get it to start again is to
> comment out all of the 'extension=' lines in my php.ini, running
> 'apachectl restart', uncommenting them, and running 'apachectl restart'
> once again. I can't get ap-ssl going because of this (apachectl sslstart
> dies a horrible, horrible death: everything else is downhill from there),
> and I don't like the idea of using IMP without it. Anybody else having
> this problem? I was using PHP4.0.3pl1 before, with pgsql support compiled
> directly in (no 'extensions'). I just upgraded to Apache 1.3.17.1 (from
> 1.3.14.1) to see if that would help but it didn't..

I am using (from a very recent pkgsrc) apache 1.3.17.1 + ap-ssl-2.8.0
+ ap-php-4.0.4.1nb1 + php-imap-4.0.4.1nb1 + imap-uw-2000.0.3nb1 +
php-pgsql-4.0.4.1nb1 + postgresql-7.0.3 + horde-1.2.4 + imp-2.2.4 with
NetBSD/i386-1.5L.  I've discovered that httpd is /very/ sensitive to
the order in which modules are loaded, and also in requiring auxiliary
shared modules to be loaded.  It took an annoying long time to figure
out the correct way to load things as there is no error log created
that tells you why httpd fails to start.  The following in httpd.conf
works for me:

	LoadModule php4_module lib/httpd/mod_php4.so
	AddModule mod_php4.c

	<IfDefine SSL>
	LoadFile !libcrypto.so
	LoadFile !libssl.so
	LoadModule ssl_module lib/httpd/mod_ssl.so
	AddModule mod_ssl.c
	</IfDefine>

	LoadFile lib/libpq.so

Plus the following in php.ini:

	extension=imap.so
	extension=pgsql.so

	Cheers,

     -- Johnny C. Lam <lamj@stat.cmu.edu>
        Department of Statistics, Carnegie Mellon University
        http://www.stat.cmu.edu/~lamj/