2-Mar-99 10:28 you wrote:
A note about php. If you choose to integrate database access for example to
mysql in the php install, then mysqld must be running for apache to start.
This is not very nice and means you must insure that upon a restart or cold
start that the database daemon is up
2-Mar-99 06:14 you wrote:
This seems like a popular combination, perhaps it would be worth someone
doing up an rpm combining these particular modules (but might be a lot of work
keeping a package with all the latest versions after each upgrade).
That sounds like it'd be a nightmare for whoever
In [EMAIL PROTECTED] User Rick ([EMAIL PROTECTED]) wrote:
2-Mar-99 10:28 you wrote:
A note about php. If you choose to integrate database access for example to
mysql in the php install, then mysqld must be running for apache to start.
This is not very nice and means you must insure that
2-Mar-99 10:28 you wrote:
A note about php. If you choose to integrate database access for example to
mysql in the php install, then mysqld must be running for apache to start.
This is not very nice and means you must insure that upon a restart or cold
start that the database daemon is
, March 02, 1999 8:20 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; Eric Gus
Subject:Re: config, compile, install help - php3, ssl, apache 1.3.x
Would it be easier to wipe my source dir and restart from scratch or can I
simply add-in php3?
Been there, done that - still can't get
On Wed, Mar 03, 1999, Juergen Rensen wrote:
I had only one little problem installing apache 1.3.4, SSLeay0.9.0b, php3
3.0.7, mod_ssl 1.3.4 and postqresql, that was, 'palloc' was defined in some
postqresql 6.3 header file that was itself included into some php3 C file
that also included a
UR I'd like to find out what is different in your build from mine. When I
UR fetched the port from FreeBSD.org, the very first time make is run, some
UR script prompted me for which databases I'd like use.
RS "the very first time make is run", "some script prompted me"... Huh. Are
you
RS sure
There is a FreeBSD port of apache 1.3.4 + php + mod_ssl which I've hacked to
include mod_frontpage. I did not include mod_perl. I spent a bit of time
building each apache 1.3.4 with each mod_ separately to observe which pieces
are patched and why. I reccommend this approach if you are going
On Mon, Mar 01, 1999, Harry Zink wrote:
I installed the apapche 1.3.4+mod_SSL rpm that is floating around on
Ralph's site - it works wonderfuly by itself, but it appears that no
other redhat modules can be installed on top of that installation. This
appears to be due to apache+mod_ssl is
At least when you compile from source you should be able to use mod_perl,
mod_php and whatever else with Apache+mod_ssl without problems.
Thanks... I'll attempt that next.
Harry
__
Apache Interface to SSLeay (mod_ssl)
This seems like a popular combination, perhaps it would be worth someone
doing up an rpm combining these particular modules (but might be a lot of work
keeping a package with all the latest versions after each upgrade).
That sounds like it'd be a nightmare for whoever would be kind enough to
Harry Zink wrote:
Would it be easier to wipe my source dir and restart from scratch or can I
simply add-in php3?
Been there, done that - still can't get it to work myself.
I installed the apapche 1.3.4+mod_SSL rpm that is floating around on
Ralph's site - it works wonderfuly by itself,
I installed the apapche 1.3.4+mod_SSL rpm that is floating around on
Ralph's site - it works wonderfuly by itself, but it appears that no
other redhat modules can be installed on top of that installation. This
appears to be due to apache+mod_ssl is using some EAPI, which is not
I've run through the list archives but can't find much of anything on
setting up the following:
under linux (slackware) 2.0.34-
apache 1.3.x
mod_ssl or openssl
ssleay ( whatever else is required)
mod_perl (I _assume_ this is needed to allow the running of perl cgi's
w/secure output)
php3
..and
14 matches
Mail list logo
