752 lines
16 KiB
HTML
752 lines
16 KiB
HTML
|
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
|
<HTML><HEAD><TITLE>Man page of sane-sharp</TITLE>
|
|
</HEAD><BODY>
|
|
<H1>sane-sharp</H1>
|
|
Section: SANE Scanner Access Now Easy (5)<BR>Updated: 11 Jul 2008<BR><A HREF="#index">Index</A>
|
|
<A HREF="/cgi-bin/man/man2html">Return to Main Contents</A><HR>
|
|
|
|
<A NAME="ixAAB"></A>
|
|
<A NAME="lbAB"> </A>
|
|
<H2>NAME</H2>
|
|
|
|
sane-sharp - SANE backend for SHARP scanners
|
|
<A NAME="lbAC"> </A>
|
|
<H2>DESCRIPTION</H2>
|
|
|
|
The
|
|
<B>sane-sharp</B>
|
|
|
|
library implements a SANE (Scanner Access Now Easy) backend that
|
|
provides access to Sharp SCSI scanners. This backend should be
|
|
considered
|
|
<B>beta-quality</B>
|
|
|
|
software! In the current state it is known to work with JX-610 and JX-250
|
|
scanners. It is prepared for usage with the JX-330 series scanners,
|
|
but we are not able to test it with these devices.
|
|
<P>
|
|
|
|
For other Sharp scanners, it may or may not work.
|
|
<P>
|
|
|
|
At present,
|
|
the following scanners are known to work with this backend.
|
|
<DL COMPACT><DT id="1"><DD>
|
|
<P>
|
|
|
|
|
|
<PRE>
|
|
Vendor Product id:
|
|
----- -----------
|
|
Sharp JX-610
|
|
Sharp JX-250
|
|
Sharp JX-320
|
|
Sharp JX-330
|
|
Sharp JX-350
|
|
</PRE>
|
|
|
|
|
|
</DL>
|
|
|
|
<P>
|
|
|
|
The following scanners are detected by the backend, but not tested:
|
|
<P>
|
|
|
|
<DL COMPACT><DT id="2"><DD>
|
|
|
|
<PRE>
|
|
Vendor Product id:
|
|
----- -----------
|
|
Sharp JX-325
|
|
</PRE>
|
|
|
|
|
|
</DL>
|
|
|
|
<A NAME="lbAD"> </A>
|
|
<H2>DEVICE NAMES</H2>
|
|
|
|
This backend expects device names of the form:
|
|
<P>
|
|
|
|
<DL COMPACT><DT id="3"><DD>
|
|
<I>special</I>
|
|
|
|
</DL>
|
|
|
|
<P>
|
|
|
|
Where
|
|
<I>special</I>
|
|
|
|
is either the path-name for the special device that corresponds to a
|
|
SCSI scanner. The special device name must be a generic SCSI device or a
|
|
symlink to such a device. Under Linux, such a device name could be
|
|
<I>/dev/sga</I>
|
|
|
|
or
|
|
<I>/dev/sge</I>,
|
|
|
|
for example. See <A HREF="/cgi-bin/man/man2html?5+sane-scsi">sane-scsi</A>(5) for details.
|
|
<P>
|
|
<A NAME="lbAE"> </A>
|
|
<H2>SCAN OPTIONS</H2>
|
|
|
|
<P>
|
|
<B>Scan Mode</B>
|
|
|
|
(parameter
|
|
<B>--mode</B>
|
|
|
|
for scanimage). Possible settings:
|
|
<DL COMPACT><DT id="4"><DD>
|
|
<B>Lineart</B>
|
|
|
|
(1 bit black & white scans),
|
|
<BR>
|
|
|
|
<B>Gray</B>
|
|
|
|
(8 bit gray scale scans),
|
|
<BR>
|
|
|
|
<B>Lineart Color</B>
|
|
|
|
(bi-level color scans),
|
|
<BR>
|
|
|
|
<B>Color</B>
|
|
|
|
(8 bit RGB scans).
|
|
</DL>
|
|
|
|
The default value is
|
|
<B>Color.</B>
|
|
|
|
<P>
|
|
<B>Halftone Pattern</B>
|
|
|
|
(parameter
|
|
<B>--halftone-pattern</B>
|
|
|
|
for scanimage). Available only for the JX-330 series scanners.
|
|
Possible settings:
|
|
<DL COMPACT><DT id="5"><DD>
|
|
<B>none</B>
|
|
|
|
<BR>
|
|
|
|
<B>Dither Bayer</B>
|
|
|
|
<BR>
|
|
|
|
<B>Dither Spiral</B>
|
|
|
|
<BR>
|
|
|
|
<B>Dither Dispersed</B>
|
|
|
|
<BR>
|
|
|
|
<B>Error Diffusion</B>
|
|
|
|
</DL>
|
|
|
|
The default value is
|
|
<B>none.</B>
|
|
|
|
<P>
|
|
<B>Paper Source</B>
|
|
|
|
(parameter
|
|
<B>--source</B>
|
|
|
|
for scanimage). This option is only available, if an automatic document
|
|
feeder or a transparency adapter is installed. Possible settings:
|
|
<DL COMPACT><DT id="6"><DD>
|
|
<B>Flatbed</B>
|
|
|
|
<BR>
|
|
|
|
<B>Automatic Document Feeder</B>
|
|
|
|
<BR>
|
|
|
|
<B>Transparency Adapter</B>
|
|
|
|
</DL>
|
|
|
|
If an ADF or a transparency adapter is installed, using it is the
|
|
default selection.
|
|
<P>
|
|
<B>Custom Gamma</B>
|
|
|
|
(parameter
|
|
<B>--custom-gamma</B>
|
|
|
|
for scanimage). This option determines whether a builtin or a custom
|
|
gamma-table is used. Possible settings:
|
|
<DL COMPACT><DT id="7"><DD>
|
|
<B>yes</B>
|
|
|
|
enables custom gamma tables
|
|
<BR>
|
|
|
|
<B>no</B>
|
|
|
|
enables a built gamma table
|
|
</DL>
|
|
|
|
<P>
|
|
<B>Gamma</B>
|
|
|
|
(parameter
|
|
<B>--Gamma</B>
|
|
|
|
for scanimage). This option is only available, if
|
|
<B>Custom Gamma</B>
|
|
|
|
is set to
|
|
<B>no.</B>
|
|
|
|
Possible values:
|
|
<DL COMPACT><DT id="8"><DD>
|
|
<B>1.0</B>
|
|
|
|
<BR>
|
|
|
|
<B>2.2</B>
|
|
|
|
</DL>
|
|
|
|
The default value is 2.2. (The JX-250 and JX-350 have no built in gamma
|
|
correction; for these scanner, a gamma table is downloaded to the scanner
|
|
by the backend.)
|
|
<P>
|
|
<B>Gamma Table</B>
|
|
|
|
(parameter
|
|
<B>--gamma-table</B>
|
|
|
|
for scanimage). Allowed values: 0..255; 256 numbers must be defined.
|
|
The default values are 0, 1, 2, .. 255 (i.e., gamma == 1). This table
|
|
is only used for gray scale scans.
|
|
<P>
|
|
<B>Red Gamma Table</B>
|
|
|
|
(parameter
|
|
<B>--red-gamma-table</B>
|
|
|
|
for scanimage). Allowed values: 0..255; 256 numbers must be defined.
|
|
The default values are 0, 1, 2, .. 255 (i.e., gamma == 1).
|
|
<P>
|
|
<B>Green Gamma Table</B>
|
|
|
|
(parameter
|
|
<B>--green-gamma-table</B>
|
|
|
|
for scanimage). Allowed values: 0..255; 256 numbers must be defined.
|
|
The default values are 0, 1, 2, .. 255 (i.e., gamma == 1).
|
|
<P>
|
|
<B>Blue Gamma Table</B>
|
|
|
|
(parameter
|
|
<B>--blue-gamma-table</B>
|
|
|
|
for scanimage). Allowed values: 0..255; 256 numbers must be defined.
|
|
The default values are 0, 1, 2, .. 255 (i.e., gamma == 1).
|
|
<P>
|
|
<B>Resolution</B>
|
|
|
|
in pixel per inch (parameter
|
|
<B>--resolution</B>
|
|
|
|
for scanimage). Selects the resolution of the scanned image. Allowed values:
|
|
<DL COMPACT><DT id="9"><DD>
|
|
<B>30..600</B>
|
|
|
|
(JX-330, JX-350 and JX-610) resp.
|
|
<B>30..400</B>
|
|
|
|
(JX-250)
|
|
</DL>
|
|
|
|
The default value is 150.
|
|
<P>
|
|
<B>Scan Window</B>
|
|
|
|
<P>
|
|
The possible settings depend on the scanner model and, for the
|
|
JX-250 and the JX-350, also on the usage of the automatic document feeder resp. the
|
|
transparency adapter. Please refer to the values allowed by xscanimage, or
|
|
xsane. With scanimage, enter one of the following commands:
|
|
<P>
|
|
<DL COMPACT><DT id="10"><DD>
|
|
<I>scanimage -d sharp --source Automatic Document Feeder --help</I>
|
|
|
|
<P>
|
|
<I>scanimage -d sharp --source Flatbed --help</I>
|
|
|
|
<P>
|
|
<I>scanimage -d sharp --source Transparency Adapter --help</I>
|
|
|
|
</DL>
|
|
|
|
<P>
|
|
in order to see the allowed parameter values for the scan window.
|
|
<P>
|
|
The scan window parameters are:
|
|
<P>
|
|
<DL COMPACT><DT id="11"><DD>
|
|
Top-left x position of scan area (parameter
|
|
<B>-l</B>
|
|
|
|
for scanimage);
|
|
<BR>
|
|
|
|
Top-left y position of scan area (parameter
|
|
<B>-t</B>
|
|
|
|
for scanimage);
|
|
<BR>
|
|
|
|
bottom right x position of scan area (parameter
|
|
<B>-x</B>
|
|
|
|
for scanimage);
|
|
<BR>
|
|
|
|
bottom right y position of scan area (parameter
|
|
<B>-y</B>
|
|
|
|
for scanimage);
|
|
</DL>
|
|
|
|
<P>
|
|
<B>Edge emphasis</B>
|
|
|
|
(parameter
|
|
<B>--Edge emphasis</B>
|
|
|
|
for scanimage). This option is not available for the JX-250 and the JX-350.
|
|
Possible settings:
|
|
<DL COMPACT><DT id="12"><DD>
|
|
<B>None</B>
|
|
|
|
<BR>
|
|
|
|
<B>Middle</B>
|
|
|
|
<BR>
|
|
|
|
<B>Strong</B>
|
|
|
|
<BR>
|
|
|
|
<B>Blur</B>
|
|
|
|
</DL>
|
|
|
|
The default value is
|
|
<B>None.</B>
|
|
|
|
<P>
|
|
<B>Threshold</B>
|
|
|
|
(parameter
|
|
<B>--threshold</B>
|
|
|
|
for scanimage). Sets the threshold for black and white pixels in lineart
|
|
mode. Possible values:
|
|
<DL COMPACT><DT id="13"><DD>
|
|
<B>1..255</B>
|
|
|
|
</DL>
|
|
|
|
The default value is
|
|
<B>128.</B>
|
|
|
|
This option is only available in scan mode lineart.
|
|
<P>
|
|
<B>Threshold Red</B>
|
|
|
|
(parameter
|
|
<B>--threshold-red</B>
|
|
|
|
for scanimage). Sets the threshold for the red component of a pixel in
|
|
in lineart color scan mode. Possible values:
|
|
<DL COMPACT><DT id="14"><DD>
|
|
<B>1..255</B>
|
|
|
|
</DL>
|
|
|
|
The default value is
|
|
<B>128.</B>
|
|
|
|
This option is only available in scan mode color lineart.
|
|
<P>
|
|
<B>Threshold Green</B>
|
|
|
|
(parameter
|
|
<B>--threshold-green</B>
|
|
|
|
for scanimage). Sets the threshold for the green component of a pixel in
|
|
in lineart color scan mode. Possible values:
|
|
<DL COMPACT><DT id="15"><DD>
|
|
<B>1..255</B>
|
|
|
|
</DL>
|
|
|
|
The default value is
|
|
<B>128.</B>
|
|
|
|
This option is only available in scan mode color lineart.
|
|
<P>
|
|
<B>Threshold Blue</B>
|
|
|
|
(parameter
|
|
<B>--threshold-blue</B>
|
|
|
|
for scanimage). Sets the threshold for the blue component of a pixel in
|
|
in lineart color scan mode. Possible values:
|
|
<DL COMPACT><DT id="16"><DD>
|
|
<B>1..255</B>
|
|
|
|
</DL>
|
|
|
|
The default value is
|
|
<B>128.</B>
|
|
|
|
This option is only available in scan mode color lineart.
|
|
<P>
|
|
<B>Light Color</B>
|
|
|
|
(parameter
|
|
<B>--LightColor</B>
|
|
|
|
for scanimage). Sets the color of the light source. Possible values:
|
|
<DL COMPACT><DT id="17"><DD>
|
|
<B>white</B>
|
|
|
|
<BR>
|
|
|
|
<B>red</B>
|
|
|
|
<BR>
|
|
|
|
<B>green</B>
|
|
|
|
<BR>
|
|
|
|
<B>blue</B>
|
|
|
|
</DL>
|
|
|
|
The default value is
|
|
<B>white.</B>
|
|
|
|
This option is only available in scan modes lineart color and color.
|
|
<P>
|
|
<A NAME="lbAF"> </A>
|
|
<H2>ADF USAGE</H2>
|
|
|
|
If a paper jam occurred, the maintenance cover
|
|
<I>must</I>
|
|
|
|
be opened and closed, even if the jammed paper can be removed without opening
|
|
the maintenance cover. Otherwise, the error condition cannot be cleared.
|
|
<P>
|
|
<A NAME="lbAG"> </A>
|
|
<H2>CONFIGURATION</H2>
|
|
|
|
The contents of the
|
|
<I>sharp.conf</I>
|
|
|
|
file is a list of options and device names that correspond to Sharp
|
|
scanners. Empty lines and lines beginning with a hash mark (#) are
|
|
ignored. See <A HREF="/cgi-bin/man/man2html?5+sane-scsi">sane-scsi</A>(5) for details about device names.
|
|
<P>
|
|
|
|
Lines setting an option start with the key word
|
|
<B>option,</B>
|
|
|
|
followed by the option's name and the option's value. At present, three
|
|
options are defined:
|
|
<B>buffers, buffersize,</B>
|
|
|
|
and
|
|
<B>readqueue.</B>
|
|
|
|
<P>
|
|
|
|
Options defined at the start of
|
|
<I>sharp.conf</I>
|
|
|
|
apply to all devices; options defined after a
|
|
device name apply to this device.
|
|
<P>
|
|
|
|
The options
|
|
<B>buffers</B>
|
|
|
|
and
|
|
<B>readqueue</B>
|
|
|
|
are only significant if the backend has been compiled
|
|
so that for each scan a second process is forked (switch
|
|
<B>USE_FORK</B>
|
|
|
|
in
|
|
<I>sharp.c</I>
|
|
|
|
). This process reads the
|
|
scan data from the scanner and writes this data into a block of shared memory.
|
|
The parent process reads the data from this memory block and delivers it
|
|
to the frontend. The options control the size and usage of this shared
|
|
memory block.
|
|
<P>
|
|
|
|
<B>option buffers</B>
|
|
|
|
defines the number of buffers used. The smallest number allowed is 2.
|
|
<P>
|
|
|
|
<B>option buffersize</B>
|
|
|
|
defines the size of one buffer. Since each buffer is filled with a
|
|
single read command sent to the scanner, its size is limited automatically
|
|
to the size allowed by the operating system or by the Sane SCSI library
|
|
for SCSI read commands. A buffer size of 128 kB or 256 kB is recommended
|
|
for scan resolutions of 300 dpi and above.
|
|
<P>
|
|
|
|
<B>option readqueue</B>
|
|
|
|
defines how many read commands to be sent to the scanner
|
|
are queued. At present, the Sane SCSI library supports queued read
|
|
commands only for for Linux. For other operating systems,
|
|
<B>option readqueue</B>
|
|
|
|
should be set to 0. For Linux,
|
|
<B>option readqueue</B>
|
|
|
|
should be set to 2. Larger values than 2 for
|
|
<B>option readqueue</B>
|
|
|
|
are not reasonable in most cases.
|
|
<B>option buffers</B>
|
|
|
|
should be greater than
|
|
<B>option readqueue.</B>
|
|
|
|
<P>
|
|
<A NAME="lbAH"> </A>
|
|
<H2>Performance Considerations</H2>
|
|
|
|
This section focuses on the problem of stops of the scanner's carriage
|
|
during a scan. Carriage stops happen mainly with the JX-250. This scanner
|
|
has obviously only a small internal buffer compared to its speed. That
|
|
means that the backend must read the data as fast as possible from the
|
|
scanner in order to avoid carriage stops.
|
|
<P>
|
|
|
|
Even the JX-250 needs only less than 10 seconds for a 400 dpi A4 gray
|
|
scale scan, which results in a data transfer rate of more than 1.6 MB
|
|
per second. This means that the data produced by the scanner must be
|
|
processed fairly fast. Due to the small internal buffer of the JX-250,
|
|
the backend must issue a read request for the next data block as soon
|
|
as possible after reading a block of data in order to avoid carriage
|
|
stops.
|
|
<P>
|
|
|
|
Stops of the carriage can be caused by the following reasons:
|
|
<P>
|
|
|
|
<DL COMPACT><DT id="18"><DD>
|
|
- too much "traffic" on the SCSI bus
|
|
<BR>
|
|
|
|
- slow responses by the backend to the scanner,
|
|
<BR>
|
|
|
|
- a program which processes the data acquired by the backend too slow.
|
|
<P>
|
|
|
|
</DL>
|
|
|
|
Too much "traffic" on the SCSI bus: This happens for example, if hard disks
|
|
are connected to the same SCSI bus as the scanner, and when data transfer
|
|
from/to these hard disks requires a considerable part of the SCSI bandwidth
|
|
during a scan. If this is the case, you should consider to connect the
|
|
scanner to a separate SCSI adapter.
|
|
<P>
|
|
|
|
Slow responses by the backend to the scanner: Unfortunately,
|
|
Unix-like operating systems generally have no real time capabilities.
|
|
Thus there is no guarantee that the backend is under any circumstances
|
|
able to communicate with the scanner as fast as required. To minimize this
|
|
problem, the backend should be compiled so that a separate reader process
|
|
is forked: Make sure that
|
|
<B>USE_FORK</B>
|
|
|
|
is defined when you compile
|
|
<I>sharp.c.</I>
|
|
|
|
If slow responses of the backend remain to be problem, you could try to
|
|
reduce the load of the system. Even while the backend and the reader
|
|
process need only a minor amount of processor time, other running
|
|
processes can cause an increase in the time delay between two time
|
|
slices given to the reader process. On slower systems, such an
|
|
increased delay can be enough to cause a carriage stop with the JX-250.
|
|
For Linux, the usage of the SG driver version 2.1.36 or above is
|
|
recommended, because it supports, in combination with
|
|
the SCSI library of Sane version 1.0.2, command queueing within the kernel.
|
|
This queueing implementation, combined with a buffer size of at least
|
|
128 kB, should avoid most carriage stops.
|
|
<P>
|
|
|
|
Slow processing of the scan data: An example for this situation is
|
|
the access to the scanner via a 10 MBit Ethernet, which is definitely
|
|
too slow to transfer the scan data as fast as they are produced by the
|
|
scanner. If you have enough memory available, you can increase
|
|
<B>option buffers,</B>
|
|
|
|
so that an entire image can be stored in these buffers.
|
|
<P>
|
|
|
|
In order to see, if the backend is too slow or if the further processing
|
|
of the data is too slow, set the environment variable
|
|
<B>SANE_DEBUG_SHARP</B>
|
|
|
|
to 1. When a scan is finished, the backend writes the line "buffer full
|
|
conditions:
|
|
<I>nn</I>
|
|
|
|
to stderr. If
|
|
<I>nn</I>
|
|
|
|
is zero, carriage stops are caused by too slow responses of the backend
|
|
or too much "traffic" on the SCSI bus. If
|
|
<I>nn</I>
|
|
|
|
is greater than zero, the backend had to wait
|
|
<I>nn</I>
|
|
|
|
times until a buffer has been processed by the frontend. (Please note that
|
|
<B>option buffers</B>
|
|
|
|
must be greater than
|
|
<B>option readqueue</B>
|
|
|
|
in order to get useful output for "buffer full conditions".)
|
|
<P>
|
|
<A NAME="lbAI"> </A>
|
|
<H2>FILES</H2>
|
|
|
|
<DL COMPACT>
|
|
<DT id="19"><I>@CONFIGDIR@/sharp.conf</I>
|
|
|
|
<DD>
|
|
The backend configuration file.
|
|
<DT id="20"><I>@LIBDIR@/libsane-sharp.a</I>
|
|
|
|
<DD>
|
|
The static library implementing this backend.
|
|
<DT id="21"><I>@LIBDIR@/libsane-sharp.so</I>
|
|
|
|
<DD>
|
|
The shared library implementing this backend (present on systems that
|
|
support dynamic loading).
|
|
</DL>
|
|
<A NAME="lbAJ"> </A>
|
|
<H2>ENVIRONMENT</H2>
|
|
|
|
<DL COMPACT>
|
|
<DT id="22"><B>SANE_DEBUG_SHARP</B>
|
|
|
|
<DD>
|
|
If the library was compiled with debug support enabled, this
|
|
environment variable controls the debug level for this backend. E.g.,
|
|
a value of 128 requests all debug output to be printed. Smaller
|
|
levels reduce verbosity.
|
|
</DL>
|
|
<A NAME="lbAK"> </A>
|
|
<H2>KNOWN PROBLEMS</H2>
|
|
|
|
1. ADF Mode
|
|
<DL COMPACT><DT id="23"><DD>
|
|
After several ADF scans, the scanner moves the carriage back to the idle
|
|
position and back to ADF scan position, before a scan starts. We do not
|
|
know, if this is a problem of the scanner, or if this is a bug of the
|
|
backend. At present, the scanner must power off and on to stop this
|
|
annoying behaviour.
|
|
</DL>
|
|
|
|
<P>
|
|
2. Threshold level does not work (only JX-610)
|
|
<P>
|
|
|
|
3. The maximum resolution is limited to 600 dpi(JX-610 supported
|
|
to 1200 dpi) resp. 400 dpi (JX-250)
|
|
<P>
|
|
|
|
4. If the JX250 is used with an ADF, the following situation can occur: After
|
|
several scans, the scanner moves, after loading a new sheet of paper, the
|
|
carriage to the idle position, and then back to the position used for ADF
|
|
scans. This happens for
|
|
<I>every</I>
|
|
|
|
scan, in contrast to the calibration, which is done after 10 scans. (For the
|
|
calibration, the carriage is also moved to the idle position.) We do not
|
|
know, if this behavior is caused by the backend, or if it is a bug in the
|
|
firmware of the scanner.
|
|
<P>
|
|
|
|
5. Usage of a transparency adapter (film scan unit) is supported, but not
|
|
tested.
|
|
<P>
|
|
<A NAME="lbAL"> </A>
|
|
<H2>SEE ALSO</H2>
|
|
|
|
<A HREF="/cgi-bin/man/man2html?7+sane">sane</A>(7), <A HREF="/cgi-bin/man/man2html?5+sane-scsi">sane-scsi</A>(5)
|
|
<A NAME="lbAM"> </A>
|
|
<H2>AUTHORS</H2>
|
|
|
|
Kazuya Fukuda, Abel Deuring
|
|
<A NAME="lbAN"> </A>
|
|
<H2>CREDITS</H2>
|
|
|
|
The Sharp backend is based on the Canon backend written by Helmut Koeberle
|
|
<P>
|
|
|
|
Parts of this man page are a plain copy of <A HREF="/cgi-bin/man/man2html?5+sane-mustek">sane-mustek</A>(5) by David
|
|
Mosberger-Tang, Andreas Czechanowski and Andreas Bolsch
|
|
<P>
|
|
|
|
<HR>
|
|
<A NAME="index"> </A><H2>Index</H2>
|
|
<DL>
|
|
<DT id="24"><A HREF="#lbAB">NAME</A><DD>
|
|
<DT id="25"><A HREF="#lbAC">DESCRIPTION</A><DD>
|
|
<DT id="26"><A HREF="#lbAD">DEVICE NAMES</A><DD>
|
|
<DT id="27"><A HREF="#lbAE">SCAN OPTIONS</A><DD>
|
|
<DT id="28"><A HREF="#lbAF">ADF USAGE</A><DD>
|
|
<DT id="29"><A HREF="#lbAG">CONFIGURATION</A><DD>
|
|
<DT id="30"><A HREF="#lbAH">Performance Considerations</A><DD>
|
|
<DT id="31"><A HREF="#lbAI">FILES</A><DD>
|
|
<DT id="32"><A HREF="#lbAJ">ENVIRONMENT</A><DD>
|
|
<DT id="33"><A HREF="#lbAK">KNOWN PROBLEMS</A><DD>
|
|
<DT id="34"><A HREF="#lbAL">SEE ALSO</A><DD>
|
|
<DT id="35"><A HREF="#lbAM">AUTHORS</A><DD>
|
|
<DT id="36"><A HREF="#lbAN">CREDITS</A><DD>
|
|
</DL>
|
|
<HR>
|
|
This document was created by
|
|
<A HREF="/cgi-bin/man/man2html">man2html</A>,
|
|
using the manual pages.<BR>
|
|
Time: 00:06:05 GMT, March 31, 2021
|
|
</BODY>
|
|
</HTML>
|