Re: config, compile, install help - php3, ssl, apache 1.3.x
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 before apache starts. Huh ? I have mysql and postgresql access compiled in PHP and in my initscripts mysqld starts AFTER httpd and postgresql is not installed at all on this server. All works just fine. __ Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/ Official Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: config, compile, install help - php3, ssl, apache 1.3.x
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 would be kind enough to create such an RPM - best solution to me still seems to create an RPM of apache 1.3.x+mod_SSL which works with standard RedHat module RPMs. As I said, not sure how feasible/easy that is to do. I have some RPMs on ftp://ftp.sch57.msk.ru/pub/redhat-addons/apache-rus There are apache (with EAPI), mod_ssl, mod_perl, PHP3 ... Unfortunatlly I can not upgrade them since I do not have RedHat anymore (I use KSI-Linux 2.0 and KSI-Linux 2.0 includes them "out of box"; you could try to grab .src.rpm s from KSI-Linux site ftp://ftp.ksi-linux.com and recompile them). __ Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/ Official Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: config, compile, install help - php3, ssl, apache 1.3.x
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 upon a restart or cold start that the database daemon is up before apache starts. Huh ? I have mysql and postgresql access compiled in PHP and in my initscripts mysqld starts AFTER httpd and postgresql is not installed at all on this server. All works just fine. 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. "the very first time make is run", "some script prompted me"... Huh. Are you sure that it's PHP *3*, not PHP/FI *2* ??? PHP 3 use standard autoconf stuff and there are no scripts to ask about databases (you could use configure script switches instead)... UR I chose mysql and continued building. Subsequent invocations of make UR did not invoke that initial script. From where this initial script come from ??? UR When I built and installed apache with php,ssl,frontpage the mysqld was UR already running. The resulting build worked. However when I rebooted, the UR apache error log contained messages indicating that php was not able to UR connect to mysqld and apache failed to start. I changed the sequence of UR starting mysqld and apache and everthing came up nicely. I kill mysqld and UR tried again, yielding the original failure. I concluded that there was a UR dependency and left it at that. I did not pursue it further. It works here even without mysql installed at all :-)) Are you sure that it's PHP *3*, not PHP/FI *2* ? __ Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/ Official Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: config, compile, install help - php3, ssl, apache 1.3.x
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 before apache starts. Huh ? I have mysql and postgresql access compiled in PHP and in my initscripts mysqld starts AFTER httpd and postgresql is not installed at all on this server. All works just fine. I'd like to find out what is different in your build from mine. When I fetched the port from FreeBSD.org, the very first time make is run, some script prompted me for which databases I'd like use. I chose mysql and continued building. Subsequent invocations of make did not invoke that initial script. When I built and installed apache with php,ssl,frontpage the mysqld was already running. The resulting build worked. However when I rebooted, the apache error log contained messages indicating that php was not able to connect to mysqld and apache failed to start. I changed the sequence of starting mysqld and apache and everthing came up nicely. I kill mysqld and tried again, yielding the original failure. I concluded that there was a dependency and left it at that. I did not pursue it further. __ Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/ Official Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
RE: config, compile, install help - php3, ssl, apache 1.3.x
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 different definition later in some apache header file (a re-definition warning is given). I checked the source and apparently there is no harm done. It helped to check the logs after httpd startup; apache mentions the configured modules there. Juergen -Original Message- From: Harry Zink [SMTP:[EMAIL PROTECTED]] Sent: Tuesday, 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 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, 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 compatible with the standard apache API - or something to that effect. Long story short - it doesn't work. I'm thinking of running two server processes - one standard apache with all the trimmings, and one just running apache-mod_ssl. The problem, of course, being that secure pages won't be able to include mod_perl, or PHP3 scripts. I'm hoping that this issue will be addressed soon, seeing as how mod_perl is kinda very important if you're running perl on your site. Harry __ OpenSSL Project http://www.openssl.org User Support Mailing List[EMAIL PROTECTED] Automated List Manager [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]
Re: config, compile, install help - php3, ssl, apache 1.3.x
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 different definition later in some apache header file (a re-definition warning is given). I checked the source and apparently there is no harm done. It helped to check the logs after httpd startup; apache mentions the configured modules there. Seems like a conflict caused by the ap_compat.h header. Because usually the symbol palloc is no longer used inside Apache (it's ap_palloc since 1.3). But PHP3 seems to use the compat stuff, so this conflict occurs.. Ralf S. Engelschall [EMAIL PROTECTED] www.engelschall.com __ Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/ Official Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: config, compile, install help - php3, ssl, apache 1.3.x
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 that it's PHP *3*, not PHP/FI *2* ??? PHP 3 use standard autoconf stuff RS and there are no scripts to ask about databases (you could use configure RS script switches instead)... Yes I am sure, php-3.0.6.tar.gz from php.net UR I chose mysql and continued building. Subsequent invocations of make UR did not invoke that initial script. URFrom where this initial script come from ??? The ports version (/usr/ports/www/apache13-php3.tar) for FreeBSD. __ Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/ Official Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: config, compile, install help - php3, ssl, apache 1.3.x
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 to integrate several mod_'s together, they tend to make different assumptions about how and what to patch in apache and its default config files. It is relatively interesting to integrate all the top level Makefiles as well. A note about the frontpage install scripts. Among the myriad of problems these scripts have, the '"'s around path names in the httpd.conf default distribution of will prevent the scripts from running. 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 before apache starts. Rick Saltzman 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 perhaps frontpage98extensions. I had a bit too hard of a time a few months back trying to get apache-ssl going, so with the docs for mod_ssl went that route and got apache1.3.3+mod_ssl up and going. Would it be easier to wipe my source dir and restart from scratch or can I simply add-in php3? I also wish to be my own CA. ANY info would be appreciated. Gus evg.org __ Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/ Official Support Mailing List [EMAIL PROTECTED] Automated List Manager [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]
Re: config, compile, install help - php3, ssl, apache 1.3.x
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 using some EAPI, which is not compatible with the standard apache API - or something to that effect. When it's a reasonable new EAPI it should work with any modules which work correctly with the standard API. Because since some weeks EAPI is able to work with standard modules, too. Long story short - it doesn't work. I'm thinking of running two server processes - one standard apache with all the trimmings, and one just running apache-mod_ssl. The problem, of course, being that secure pages won't be able to include mod_perl, or PHP3 scripts. I'm hoping that this issue will be addressed soon, seeing as how mod_perl is kinda very important if you're running perl on your site. I recommend you to compile your own Apache+mod_ssl+mod_perl+whatever from the source instead of using precompiled RPMs. As the website indicates, the RPMs are _contributed_ stuff I cannot not officially support (because I cannot test it myself and binaries always cause too much problems). 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. Ralf S. Engelschall [EMAIL PROTECTED] www.engelschall.com __ Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/ Official Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: config, compile, install help - php3, ssl, apache 1.3.x
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) www.engelschall.com/sw/mod_ssl/ Official Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: config, compile, install help - php3, ssl, apache 1.3.x
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 create such an RPM - best solution to me still seems to create an RPM of apache 1.3.x+mod_SSL which works with standard RedHat module RPMs. As I said, not sure how feasible/easy that is to do. Harry __ Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/ Official Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: config, compile, install help - php3, ssl, apache 1.3.x
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, 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 compatible with the standard apache API - or something to that effect. Long story short - it doesn't work. I'm thinking of running two server processes - one standard apache with all the trimmings, and one just running apache-mod_ssl. The problem, of course, being that secure pages won't be able to include mod_perl, or PHP3 scripts. I'm hoping that this issue will be addressed soon, seeing as how mod_perl is kinda very important if you're running perl on your site. AFAIK, this problem doesn't affect Apache-SSL. Cheers, Ben. -- http://www.apache-ssl.org/ben.html "My grandfather once told me that there are two kinds of people: those who work and those who take the credit. He told me to try to be in the first group; there was less competition there." - Indira Gandhi __ Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/ Official Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: config, compile, install help - php3, ssl, apache 1.3.x
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 compatible with the standard apache API - or something to that effect. Long story short - it doesn't work. Download the sources and compile with all the modules you list. I run that exact setup here (apache+mod_ssl/PHP3/mod_perl) and it works perfectly, and yes, SSL can use PHP/mod_perl with this setup. It is really not that difficult to do, the INSTALL docs on all these packages are pretty straightforward and simple (or if you are really hard pressed on doing this contact me offlist and I or one of my staff can possibly assist you). 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). -- E-Mail: William X. Walsh [EMAIL PROTECTED] Date: 02-Mar-99 Time: 02:11:54 -- "We may well be on our way to a society overrun by hordes of lawyers, hungry as locusts." - Chief Justice Warren Burger, US Supreme Court, 1977 __ Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/ Official Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
