Date: Wed Jul 10 12:19:42 CEST 2002
User: Derick Rethans
Directory: srmdoc/articles
Log Message:
[0.05]
- Fix spelling error, use proper name for "PHP 4".
Modified files:
srmdoc/articles/idiot-guide.xml (version: 1.5)
[FILE: /srmdoc/articles/idiot-guide.xml]
--- srmdoc/articles/idiot-guide.xml:1.4 Wed Jul 10 07:25:51 2002 GMT
+++ srmdoc/articles/idiot-guide.xml Wed Jul 10 08:19:41 2002 GMT
@@ -4,7 +4,7 @@
<!ENTITY % srmdoc.defs SYSTEM "../global.ent">
%srmdoc.defs;
]>
-<!-- $Revision: 1.4 $ -->
+<!-- $Revision: 1.5 $ -->
<article>
<articleinfo>
<author>
@@ -36,7 +36,7 @@
<authorinitials>ja</authorinitials>
<revremark>
Added a new entry in the FAQ about the error that happens
- when trying to use aphp built with apache.
+ when trying to use a PHP built with Apache.
</revremark>
</revision>
</revhistory>
@@ -328,7 +328,7 @@
<title>DO NOT SYMLINK!</title>
<para>
I know it seems like a good idea to just make a symlink
- in the php4 directory to the srm_sapi and php_srm directory,
+ in the PHP 4 directory to the srm_sapi and php_srm directory,
but its not! Apparently "make clean" does not
clean out symlinked directories.
</para>
@@ -348,7 +348,7 @@
./buildconf
</programlisting>
<para>
- in the php4 directory. This builds the php4 configure.
+ in the PHP 4 directory. This builds the PHP 4 configure.
</para>
<para>
@@ -584,7 +584,7 @@
<title>Serve Me up, Compiling PHP</title>
<para>
Did you <programlisting>make clean</programlisting> and
- <programlisting>make distclean</programlisting> in your php4 source
+ <programlisting>make distclean</programlisting> in your PHP 4 source
directory yet? no? Bad admin! No Cookie!
</para>
@@ -680,7 +680,7 @@
<para>
The next test should be to make sure you can run Banana's and
- functions within SRM's copy of php. There are two files
+ functions within SRM's copy of PHP. There are two files
included in this package that will help you test out SRM, and
make sure that it works. One is called uptime.php (which is a
modification of the origignal uptime.php on the SRM website.)
@@ -725,7 +725,7 @@
</question>
<answer>
<para> Weather or not you use session handling, SRM itself does.
- What is going on is that php cannot use your session save
+ What is going on is that PHP cannot use your session save
handler, and you probably set it to something like "file"
instead of "files" or "srm".</para>
</answer>
@@ -733,14 +733,14 @@
<qandaentry>
<question>
<para>
- I get the error " Cannot open module:
- /usr/local/srm/lib/srm_php4.so: undefined symbol: ap_block_alarms
- " in the srm logs when I run srmd.
+ I get the error "Cannot open module:
+ /usr/local/srm/lib/srm_php4.so: undefined symbol: ap_block_alarms"
+ in the SRM logs when I run srmd.
</para>
</question>
<answer>
<para> You either forgot to "make clean" inbetween building
- the php for apache and the php for srm, or you are trying to compile
+ the PHP for Apache and the PHP for SRM, or you are trying to compile
srm --with-apxs and --with-srm-sapi.
</para>
</answer>
@@ -764,24 +764,6 @@
</para>
</section>
</article>
-<!-- $Log: cvstemp,v $
-<!-- Revision 1.4 2002/07/10 09:25:51 jonny
-<!-- Added a qandaentry about using an apache sapi compiled php with srmd.
-<!--
-<!-- Revision 1.3 2002/07/04 20:41:40 jonny
-<!-- [0.11]
-<!-- - Fixed the title "Insalling" to "Installing". Oopsie.
-<!-- (Jonathan Arkell)
-<!--
-<!-- Revision 1.2 2002/06/25 13:32:56 derick
-<!-- [0.10]
-<!-- - Fix docs
-<!--
-<!-- Revision 1.1 2002/06/20 07:36:49 derick
-<!-- [1.00]
-<!-- - Added the idiot guide to the CVS
-<!-- -->
-
<!-- keep this comment at the end of the file
vim600: syn=xml fen fdm=syntax fdl=4 si
vim: et tw=78 syn=sgml
Received on Wed Jul 10 13:03:55 2002
This archive was generated by hypermail 2.1.8 : Tue Jan 06 2009 - 02:00:03 CET