<arg><option>--password password</option></arg>
<arg><option>--host HOST_NAME</option></arg>
<arg><option>--proxy PROXY:PORT</option></arg>
+ <arg><option>--logfile LOGFILE</option></arg>
<arg><option>--bash</option></arg>
<arg><option>--debug</option></arg>
<arg><option>--version</option></arg>
</para>
</listitem>
</varlistentry>
+ <varlistentry>
+ <term><option>--logfile LOGFILE</option></term>
+ <listitem>
+ <para>
+ Specify a logfile for bti to write status messages to. LOGFILE
+ is in relation to the user's home directory, not an absolute
+ path to a file.
+ </para>
+ </listitem>
+ </varlistentry>
<varlistentry>
<term><option>--debug</option></term>
<listitem>
</para>
</listitem>
</varlistentry>
+ <varlistentry>
+ <term><option>logfile</option></term>
+ <listitem>
+ <para>
+ The logfile name for bti to write what happened to.
+ This file is relative to the user's home directory. If this
+ file is not specified here or on the command line, no logging
+ will be written to the disk.
+ </para>
+ </listitem>
+ </varlistentry>
</variablelist>
<para>
There is an example config file called