<chapter id="administration">
- <!-- $Id: administration.xml,v 1.4 2002-04-09 19:20:22 adam Exp $ -->
+ <!-- $Id: administration.xml,v 1.7 2002-10-10 14:27:18 heikki Exp $ -->
<title>Administrating Zebra</title>
<para>
</para>
<para>
+ FIXME - Didn't Adam make something to have multiple databases in multiple dirs...
+ </para>
+
+ <para>
<variablelist>
<varlistentry>
<listitem>
<para>
Specifies the Z39.50 database name.
+ FIXME - now we can have multiple databases in one server. -H
</para>
</listitem>
</varlistentry>
in the configuration file. In addition, you should set
<literal>storeKeys</literal> to <literal>1</literal>, since the Zebra
indexer must save additional information about the contents of each record
- in order to modify the indices correctly at a later time.
+ in order to modify the indexes correctly at a later time.
</para>
+ <!--FIXME - There must be a simpler way to do this with Adams string tags -H
+ -->
+
<para>
For example, to update records of group <literal>esdd</literal>
located below
each directory in the order specified and use the next specified
directories as needed.
The <emphasis>size</emphasis> is an integer followed by a qualifier
- code, <literal>M</literal> for megabytes,
+ code,
+ <literal>b</literal> for bytes,
<literal>k</literal> for kilobytes.
+ <literal>M</literal> for megabytes,
+ <literal>G</literal> for gigabytes.
</para>
<para>
For instance, if you have allocated two disks for your register, and
the first disk is mounted
- on <literal>/d1</literal> and has 200 MB of free space and the
- second, mounted on <literal>/d2</literal> has 300 MB, you could
+ on <literal>/d1</literal> and has 2GB of free space and the
+ second, mounted on <literal>/d2</literal> has 3.6 GB, you could
put this entry in your configuration file:
<screen>
- register: /d1:200M /d2:300M
+ register: /d1:2G /d2:3600M
</screen>
</para>
In order to make changes to the system take effect for the
users, you'll have to submit a "commit" command after a
(sequence of) update operation(s).
- You can ask the indexer to commit the changes immediately
- after the update operation:
</para>
<para>
<screen>
- $ zebraidx update /d1/records update /d2/more-records commit
+ $ zebraidx update /d1/records
+ $ zebraidx commit
</screen>
</para>
<para>
<screen>
- $ zebraidx -g books update /d1/records update /d2/more-records
+ $ zebraidx -g books update /d1/records /d2/more-records
$ zebraidx -g fun update /d3/fun-records
$ zebraidx commit
</screen>