Date: Wed Feb 20 18:59:32 CET 2002
User: Dan Kalowsky
Directory: srm
Log Message:
[1.07]
- I did the time right Derick! More grammatical fixes
Modified files:
srm/HOWTO (version: 1.3)
[FILE: /srm/HOWTO]
--- srm/HOWTO:1.2 Wed Feb 20 16:04:33 2002 GMT
+++ srm/HOWTO Wed Feb 20 16:59:31 2002 GMT
@@ -17,9 +17,9 @@
2) ABOUT
This file is designed to help you with installing Vulcan-Logic SRM.
- Due to the examples, the active config file is not identical to the
- default SRM config. While using this document it is assumed that
- you have compiled PHP & Apache before, and this isn't your first
+ Due to the examples, the active configuration is not identical to the
+ default SRM configuration. While using this document it is assumed
+ that you have compiled PHP & Apache before, and this isn't your first
install on a unix/linux system. If this isn't true, please read one
or two documents explaining install of PHP before.
@@ -48,91 +48,99 @@
4) INSTALLATION
4.1) COMPILING
- Here you find all steps needed to compile a srmd, PHP as running machine in this srmd and
- ofcourse PHP for accessing SRM
+ 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 choose the configure options you want (remember,
- ./configure --help shows 'em all.
- in this Example we choose to use to following configure line:
+ 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 default path for srm. it is just to make it easier for you
- to follow this document.)
+ 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, you should make & install srm by doing:
+ After configure, it is posisble to make and install srm by doing:
- make; make install;
+ make && make install;
- Now edit your srm.ini, (make sure that paths are changed from /usr/local/srm... to /srm...)
- comment "http" module out, it isnt included in spring nights.
- (Hint: if you want to testdrive srm at this moment, comment "php4" module out)
- (2. Hint: if you commented "php4" module out, and you want to go on with this document
- well, uncomment it ,)
+ 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.
+
+ If you want to testdrive srm at this point, comment the "php4"
+ module out. You will need to uncomment this section if you want to go
+ on with this document.
4.1.2) COMPILING PHP
- First you should recreate the configure file of PHP, just change into the directory php-4.1.1,
- delete configure script and run buildconf:
+ 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
- Now doing a:
- ./configure --help |grep srm
+ 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
- should show you some lines, if the lines below are show, everything is fine,
- if not, have a look at the TROUBLESHOOTING section of this file.
+ 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
- Well, first change to the PHP Source directory,
- then we configure PHP as we need it. in this example this are just the essentials
- srm needs to run (and additional the prefix where all those nice files should go ;)
+ 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 do
+ Now the PHP system is ready to be compiled. To compile do:
- make; make install;
+ make && make install;
- again, after that php module for srmd should be in right place,
- now you may start your srmd by changing to /srm/sbin
- and running it (see 5, RUNNING)
+ 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 real simple,
- just move again to your php source,
- and configure with following options:
+ 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
- (Ive choosen CGI Build of PHP and a directory that wouldnt change
- anything at your running PHP System, i guess youre able to
- change it to fit your needs)
+
+ This configure chooses a CGI build of PHP and a directory that won't
+ change anything of your running PHP System.
5) RUNNING
cd /srm/sbin/; ./srmd -X -L
- (for testing -X -L no bad idea, because you can see what happens then
+
+ 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 -X -L to see what happens.
- If srmd hangs at startup, check if it still hangs if you comment php module out
- if so, check with which extensions you compiled it, and play arround a bit
- (in special with self-written extension) by not configuring some.. then
- youll find out which of the extensions could cause this trouble)
+ 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.
7) BUG REPORTING
- If you have any Bugs, Suggestions, Ideas:
+ If you have any Bugs, Suggestions, or Ideas:
srm@lists.vl-srm.net
- Please make sure you include as much Details as possible
+ Please make sure you include as many details as possible
in your report.
Received on Wed Feb 20 18:59:23 2002
This archive was generated by hypermail 2.1.8 : Tue Jan 06 2009 - 03:00:03 CET