CTDB_BASE should only ever be modified by test code. It should not be
mentioned in the user documentation.
Signed-off-by: Martin Schwenke <martin@meltin.net>
Reviewed-by: Amitay Isaacs <amitay@gmail.com>
<variablelist>
- <varlistentry>
- <term>CTDB_BASE=<parameter>DIRECTORY</parameter></term>
- <listitem>
- <para>
- DIRECTORY containing CTDB scripts and configuration files.
- </para>
- </listitem>
- </varlistentry>
-
<varlistentry>
<term>CTDB_INIT_STYLE=debian|redhat|suse</term>
<listitem>
an event script times out.
</para>
<para>
- Default is <filename><varname>CTDB_BASE</varname>/debug-hung-script.sh</filename>.
+ Default is <filename>/usr/local/etc/ctdb/debug-hung-script.sh</filename>.
</para>
</listitem>
</varlistentry>
</para>
<para>
No default, usually
- <filename><varname>CTDB_BASE</varname>/debug_locks.sh</filename>.
+ <filename>/usr/local/etc/ctdb/debug_locks.sh</filename>.
</para>
</listitem>
</varlistentry>
</screen>
</refsect1>
- <refsect1>
- <title>ENVIRONMENT</title>
-
- <variablelist>
- <varlistentry><term><envar>CTDB_BASE</envar></term>
- <listitem>
- <para>
- Directory containing CTDB configuration files. The
- default is <filename>/usr/local/etc/ctdb</filename>.
- </para>
- </listitem>
- </varlistentry>
-
- </variablelist>
- </refsect1>
-
<refsect1>
<title>FILES</title>
is given precedence. If a
relative path is specified and no corresponding file
exists relative to the current directory then the file is
- also searched for in the <filename>$CTDB_BASE</filename>
- directory.
+ also searched for in the CTDB configuration directory.
</para>
<para>
Otherwise the default is