1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
|
#! /bin/sh -e
## 06-DocDirectoriesForDebian.dpatch by Raphael Bossek <bossekr@debian.org>
##
## All lines beginning with `## DP:' are a description of the patch.
## DP: Change documentation to match installation on Debian GNU/Linux.
if [ $# -lt 1 ]; then
echo "`basename $0`: script expects -patch|-unpatch as argument" >&2
exit 1
fi
[ -f debian/patches/00patch-opts ] && . debian/patches/00patch-opts
patch_opts="${patch_opts:--f --no-backup-if-mismatch} ${2:+-d $2}"
case "$1" in
-patch) patch -p0 ${patch_opts} < $0;;
-unpatch) patch -R -p0 ${patch_opts} < $0;;
*)
echo "`basename $0`: script expects -patch|-unpatch as argument" >&2
exit 1;;
esac
exit 0
@DPATCH@
diff -urNad 4Suite.orig/docs/xml/HowTos/QuickStart.doc 4Suite/docs/xml/HowTos/QuickStart.doc
--- 4Suite.orig/docs/xml/HowTos/QuickStart.doc Tue Feb 17 04:04:46 2004
+++ 4Suite/docs/xml/HowTos/QuickStart.doc Mon May 31 17:58:57 2004
@@ -117,7 +117,7 @@
<section>
<title>Create the Configuration File</title>
<para>The repository and model are never accessed directly; all communication with them is done via a network server called the Controller, or "4ssd". This daemon listens on a certain port (8803, by default) and uses a custom RPC protocol ("FtRpc") for request/response communication.</para>
- <para>The controller needs a configuration file to tell it what driver to use for accessing the database (FlatFile or Postgres), where the database is, where to put the log file, etc. Sample config files for Windows and Unix are provided in the appendices of this document, and they are also provided in the 4Suite distribution; on Unix look for {PYTHON_HOME}/.../4ss.conf, and on Windows look for C:\Python23\Share\Settings\4Suite\4ss.conf.</para>
+ <para>The controller needs a configuration file to tell it what driver to use for accessing the database (FlatFile or Postgres), where the database is, where to put the log file, etc. Sample config files for Windows and Unix are provided in the appendices of this document, and they are also provided in the 4Suite distribution; on Unix look for /etc/4Suite/4ss.conf, and on Windows look for C:\Python23\Share\Settings\4Suite\4ss.conf.</para>
<orderedlist>
<listitem>
<para>Use one of the sample configuration files in the appendices below, making adjustments to the LogFile and PidFile elements as necessary (set these to wherever you want the files to be created). Save the config on your system anywhere, under any name. We typically call it "4ss.conf", but the name really doesn't matter.</para>
@@ -126,7 +126,7 @@
<para>Now set the environment variable FTSERVER_CONFIG_FILE to be the full path to the file. For example, if you put the file at /usr/local/etc/4ss.conf, then that's what you'd set FTSERVER_CONFIG_FILE to. If you put it at C:\temp\4ss.conf, then use that. This environment variable <emphasis>must</emphasis> be set.</para>
</listitem>
<listitem>
- <para>If you are using FlatFile (you probably are, since these directions don't tell you otherwise), then you may want to set the environment variable FT_DATABASE_DIR. This variable tells 4Suite where to look for the FlatFile databases, so set it to the directory where you want the files to be stored. If FT_DATABASE_DIR isn't set, then the default will be {python}/Ft/Share/Data/FlatFile.</para>
+ <para>If you are using FlatFile (you probably are, since these directions don't tell you otherwise), then you may want to set the environment variable FT_DATABASE_DIR. This variable tells 4Suite where to look for the FlatFile databases, so set it to the directory where you want the files to be stored. If FT_DATABASE_DIR isn't set, then the default will be /var/lib/4Suite/FlatFile.</para>
</listitem>
</orderedlist>
</section>
|
