<title>Administrating Zebra</title>
<!-- ### It's a bit daft that this chapter (which describes half of
the configuration-file formats) is separated from
<title>Administrating Zebra</title>
<!-- ### It's a bit daft that this chapter (which describes half of
the configuration-file formats) is separated from
Specifies a file with description of user accounts for Zebra.
File format is similar to that used by the passwd directive except
that the password are encrypted. Use Apache's htpasswd or similar
Specifies a file with description of user accounts for Zebra.
File format is similar to that used by the passwd directive except
that the password are encrypted. Use Apache's htpasswd or similar
to access Zebra via the passwd system. There are two kinds
of permissions currently: read (r) and write(w). By default
users not listed in a permission directive are given the read
to access Zebra via the passwd system. There are two kinds
of permissions currently: read (r) and write(w). By default
users not listed in a permission directive are given the read
username, or Z39.50 anonymous style use
<literal>anonymous</literal>. The permstring consists of
a sequence of characters. Include character <literal>w</literal>
username, or Z39.50 anonymous style use
<literal>anonymous</literal>. The permstring consists of
a sequence of characters. Include character <literal>w</literal>
server using the <ulink url="&url.z39.50;">Z39.50</ulink>
protocol. The <ulink url="&url.sru;">SRU</ulink> protocol does
not support extended services.
server using the <ulink url="&url.z39.50;">Z39.50</ulink>
protocol. The <ulink url="&url.sru;">SRU</ulink> protocol does
not support extended services.
</screen>
The general record type should be set to any record filter which
is able to parse XML records, you may use any of the two
</screen>
The general record type should be set to any record filter which
is able to parse XML records, you may use any of the two
<note>It is not possible to carry information about record types or
similar to Zebra when using extended services, due to
limitations of the <ulink url="&url.z39.50;">Z39.50</ulink>
<note>It is not possible to carry information about record types or
similar to Zebra when using extended services, due to
limitations of the <ulink url="&url.z39.50;">Z39.50</ulink>
per-record basis. One and only one general XML indexing filter
must be defined.
<!-- but because it is represented as an OID, we would need some
per-record basis. One and only one general XML indexing filter
must be defined.
<!-- but because it is represented as an OID, we would need some
servers to accept special binary <emphasis>extended services</emphasis>
protocol packages, which may be used to insert, update and delete
records into servers. These carry control and update
servers to accept special binary <emphasis>extended services</emphasis>
protocol packages, which may be used to insert, update and delete
records into servers. These carry control and update