Date: Wed Feb 20 19:07:22 CET 2002
User: Derick Rethans
Directory: srm
Log Message:
[0.25]
- Rewrite the TROUBLESHOOTING section
Modified files:
srm/HOWTO (version: 1.4)
[FILE: /srm/HOWTO]
--- srm/HOWTO:1.3 Wed Feb 20 16:59:31 2002 GMT
+++ srm/HOWTO Wed Feb 20 17:07:22 2002 GMT
@@ -1,4 +1,4 @@
-1) INDEX:
+1) INDEX
- 1. INDEX
- 2. ABOUT
@@ -25,6 +25,7 @@
3) FILES
+
This example uses a very basic install of PHP & SRM, requiring only
3 Files:
@@ -35,7 +36,7 @@
These 3 files need to be extracted, the easiest way to accomplish this
would be to use the following commands (assuming you have them in same
directory):
-
+
tar -xzf php-4.1.1.tar.gz
mv srm-php-0.6.0.tar.gz php-4.1.1; cd php-4.1.1; \
tar -xzf srm-php-0.6.0.tar.gz; cd ..
@@ -48,23 +49,26 @@
4) INSTALLATION
4.1) COMPILING
+
This section discusses all the steps needed to compile srmd, and PHP
as a running machine.
+
4.1.1) COMPILING SRM
+
First change to SRM Source directory, then select the configure
options you want (remember, ./configure --help shows them all).
For this example the following configure line is used:
-
+
./configure --prefix=/srm --enable-auth
-
+
Please remember, /srm is not the default path for srm. It's just being
used to make it easier for you to follow this document.
-
+
After configure, it is posisble to make and install srm by doing:
-
+
make && make install;
-
+
Now to customize the srm.ini. Ensure that the paths are changed from
/usr/local/srm... to /srm for this example. Comment the "http"
module out, it isnt included in the Spring Nights release.
@@ -75,45 +79,48 @@
4.1.2) COMPILING PHP
+
First you should recreate the PHP configure file. Change into
the php-4.1.1 directory, delete configure script, and run buildconf:
cd php-4.1.1; rm -f configure; ./buildconf
-
+
It is now possible configure PHP with a clean configure script. To
find out what options are needed for compiling with SRM, type:
./configure --help | grep srm
-
+
If the lines below are shown everything is fine, otherwise have a look
at the TROUBLESHOOTING section of this file.
--with-srm-sapi[=DIR] Include SRM-SAPI support
- --with-srm[=DIR] Include SRM: Script Running Magic
- (http://www.vl-srm.net/) support
+ --with-srm[=DIR] Include SRM: Script Running Magic
+ (http://www.vl-srm.net/) support
+
+4.1.2.1) COMPILING PHP - SRM SAPI
-4.1.2.1) COMPILING PHP - SRM SAPI
First change to the PHP Source directory, and configure PHP as
necessary. This example uses just the essentials srm needs
to run (and the additional prefix where all those nice files should
go):
-
+
./configure --with-srm-sapi=/srm --with-srm=/srm --prefix=/srm
-
+
Now the PHP system is ready to be compiled. To compile do:
-
+
make && make install;
-
+
After the 'make install' is completed, the php module for srmd should
be in the proper place. Now you may start srmd by changing to
/srm/sbin and running it (see section 5, RUNNING).
4.1.2.2) COMPILING PHP - SRM EXTENDED
+
Ok, compiling PHP with SRM extension is not any more difficult. Change
directories again to the php source, and run configure with following
options:
-
+
./configure --with-srm=/srm --prefix=/srm/php-extended
This configure chooses a CGI build of PHP and a directory that won't
@@ -121,26 +128,25 @@
5) RUNNING
+ cd /srm/sbin/; ./srmd -X -L
- cd /srm/sbin/; ./srmd -X -L
-
- For testing the -X -L options are not bad idea. These allow you to
+ For testing the -X -L options are not bad idea. These allow you to
see what is happening.
6) TROUBLESHOOTING
- If srmd doesnt start, try the -X -L options to see what has caused the
- daemon to fail. If srmd hangs at startup, try commenting the php
- module out, checking which extensions are compiled in, and playing
- around (particularly with self-written extensions) by not configuring
- some. This will then allow you find out which of the extensions might
- be causing this trouble.
+ If the SRM daemon does not start, you can try the -X (do not run as
+ daemon) and/or -L (log to screen) to see what has caused the
+ daemon to fail. If the SRM daemon hangs at startup, you can try commenting
+ out the PHP module from the configuration file (srm.ini). It might be that
+ one of the extensions (particulairy self-written extensions) you compiled
+ in into PHP cause a problem.
7) BUG REPORTING
If you have any Bugs, Suggestions, or Ideas:
srm@lists.vl-srm.net
-
- Please make sure you include as many details as possible
- in your report.
+
+ Please make sure you include as many details as possible in your report.
+
Received on Wed Feb 20 19:07:15 2002
This archive was generated by hypermail 2.1.8 : Tue Jan 06 2009 - 03:00:03 CET