<literal>your.company.com</literal> like this:
</para>
<screen>
- yaz-proxy -a - -t tcp:foo.bar.com:18398 tcp:@:9000
+ yazproxy -a - -t tcp:foo.bar.com:18398 tcp:@:9000
</screen>
<para>
(The <literal>-a -</literal> option requests APDU logging on
order for the config file facility to be enabled.
</para>
<tip>
- <para>To check for a config file to be well-formed, the yaz-proxy may
+ <para>To check for a config file to be well-formed, the yazproxy may
be invoked without specifying a listening port, i.e.
<screen>
- yaz-proxy -c myconfig.xml
+ yazproxy -c myconfig.xml
</screen>
If this does not produce errors, the file is well-formed.
</para>
<title>Proxy Usage</title>
<para>
</para>
- <refentry id="yaz-proxy">
+ <refentry id="yazproxy-ref">
&yaz-proxy-ref;
</refentry>
</section>
<refmeta>
- <refentrytitle>yaz-proxy</refentrytitle>
+ <refentrytitle>yazproxy</refentrytitle>
<manvolnum>8</manvolnum>
</refmeta>
<refnamediv>
- <refname>yaz-proxy</refname>
+ <refname>yazproxy</refname>
<refpurpose>The YAZ toolkit's transparent Z39.50 proxy</refpurpose>
</refnamediv>
<refsynopsisdiv>
<cmdsynopsis>
- <command>yaz-proxy</command>
+ <command>yazproxy</command>
<arg choice="opt">-a <replaceable>filename</replaceable></arg>
<arg choice="opt">-l <replaceable>filename</replaceable></arg>
<arg choice="opt">-m <replaceable>num</replaceable></arg>
<refsect1><title>DESCRIPTION</title>
<para>
- <command>yaz-proxy</command> is a Z39.50 optimizing proxy daemon.
+ <command>yazproxy</command> is a Z39.50 optimizing proxy daemon.
The listening port must be specified on the command-line.
<command>inetd</command> operation is not supported.
The <replaceable>host</replaceable>:<replaceable>port</replaceable>
to listen for connections coming from any address.
</para>
<para>
- <command>yaz-proxy</command> can be configured using command-line
+ <command>yazproxy</command> can be configured using command-line
options or a configuration file.
Configuration file options override values specified
on the command-line.
</para>
<para>
- <command>yaz-proxy</command> rereads its configuration file and
+ <command>yazproxy</command> rereads its configuration file and
reopens log files when it receives the hangup signal, SIGHUP.
</para>
</refsect1>
</varlistentry>
<varlistentry><term>-p <replaceable>pidfile</replaceable></term>
<listitem><para>
- When specified, yaz-proxy will create <replaceable>pidfile</replaceable>
+ When specified, yazproxy will create <replaceable>pidfile</replaceable>
with the process ID of the proxy. The pidfile will be generated
before the process changes identity (see option <literal>-u</literal>).
</para></listitem>
</varlistentry>
<varlistentry><term>-u <replaceable>userid</replaceable></term>
<listitem><para>
- When specified, yaz-proxy will change identity to the user ID
+ When specified, yazproxy will change identity to the user ID
specified, just after the proxy has started listening to a
possibly privileged port and after the PID file has been created
if specified by option <literal>-u</literal>.
Congress bibliographic server:
</para>
<screen>
- $ yaz-proxy -t z3950.loc.gov:7090 @:9000
+ $ yazproxy -t z3950.loc.gov:7090 @:9000
</screen>
<para>
The LOC target is sometimes very slow. You can connect to