kopia lustrzana https://gitlab.com/sane-project/website
updates for sane-backends 1.0.24
m. allan noah
rodzic
3c651aaa43
commit
7f6bd48a06
25
index.html
25
index.html
|
|
@ -36,21 +36,19 @@
|
|||
<td valign=top bgcolor="#e0e0ff" width="300">
|
||||
<h3>Latest News</h3>
|
||||
<p>
|
||||
<strong>2012-08-19:</strong>
|
||||
<a href="source.html">SANE-Backends-1.0.23</a> has been released. Changes since 1.0.22:
|
||||
<strong>2013-09-30:</strong>
|
||||
<a href="source.html">SANE-Backends-1.0.24</a> has been released. Changes since 1.0.23:
|
||||
</p>
|
||||
<ul>
|
||||
<li>New backends: kvs40xx (Panasonic KV-S40xx), kodakaio (Kodak AiO ESP and Hero)</li>
|
||||
<li>Significant enhancements to several backends</li>
|
||||
<li>30 new scanner models supported</li>
|
||||
<li>V4L support improvements</li>
|
||||
<li>Improvements for builds on multiple platforms</li>
|
||||
<li>Improved udev rules</li>
|
||||
<li>Updated software deskew algorithm</li>
|
||||
<li>Documentation updates</li>
|
||||
<li>Bugfixes</li>
|
||||
<li>Significant enhancements to pixma, genesys, kodakaio, fujitsu, canon_dr.
|
||||
<li>Minor updates, bugfixes or scanners added in several backends.
|
||||
<li>Added new testsuite
|
||||
<li>51 new scanner models supported.
|
||||
<li>USB support improvements.
|
||||
<li>Improved build system (mingw64, bug fixes, default pthread on Linux).
|
||||
<li>Documentation updates.
|
||||
<li>Bugfixes.
|
||||
</ul>
|
||||
<b>Note:</b> Due to problems with file downloads at alioth, the sane-backends source tarball has been divided into multiple parts. Directions for assembling these are provided in README.txt with <a href="source.html">the downloads</a>.
|
||||
</td>
|
||||
|
||||
<td valign=top>
|
||||
|
|
@ -82,8 +80,5 @@
|
|||
<a href="imprint.html">Contact</a>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
<font size="-1">$Date$ $Author$</font>
|
||||
</p>
|
||||
</body>
|
||||
</html>
|
||||
|
|
|
|||
|
|
@ -20,8 +20,8 @@
|
|||
The <B>sane-canon_dr</B> library implements a SANE (Scanner Access Now Easy)
|
||||
backend which provides access to some Canon DR-series scanners.
|
||||
|
||||
This document describes backend version 37, which shipped with SANE
|
||||
1.0.22.
|
||||
This document describes backend version 41, which shipped with SANE
|
||||
1.0.24.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -152,6 +152,12 @@
|
|||
bytes. Enable this option if the scanner fails to respond to
|
||||
commands.
|
||||
|
||||
"option duplex-offset [integer]"
|
||||
Some scanners pad the upper edge of one side of a duplex scan.
|
||||
There is some variation in the amount of padding. Modify this
|
||||
option if your unit shows an unwanted band of image data on only
|
||||
one side.
|
||||
|
||||
Note: 'option' lines may appear multiple times in the configuration
|
||||
file. They only apply to scanners discovered by the next 'scsi/usb'
|
||||
line.
|
||||
|
|
@ -188,6 +194,7 @@
|
|||
HPrint hprint.com.br provided funding and testing for DR-2510 support
|
||||
Stone-IT www.stone-it.com provided funding for DR-2010 and DR-2050 sup‐
|
||||
port
|
||||
Gerhard Pfeffer provided access and testing for P-208 and P-215
|
||||
Special thanks to: Alejandro Imass, Andre Shimakawa, Martijn van Brum‐
|
||||
melen, Thanos Diacakis and Junren Shi for testing and feedback.
|
||||
|
||||
|
|
@ -201,7 +208,7 @@
|
|||
<H2>AUTHOR</H2><PRE>
|
||||
m. allan noah: <kitno455 a t gmail d o t com>
|
||||
|
||||
26 Jan 2011 <B><A HREF="sane-canon_dr.5.html">sane-canon_dr(5)</A></B>
|
||||
16 Sep 2013 <B><A HREF="sane-canon_dr.5.html">sane-canon_dr(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -54,6 +54,12 @@
|
|||
pnm
|
||||
mustek
|
||||
|
||||
It is also possible to add a file in <I>/etc/sane.d/dll.d</I> that contains
|
||||
the list of backends to be added. Backends mentioned in a file included
|
||||
in this directory will be added before any backends listed in <I>dll.conf.</I>
|
||||
Files in <I>/etc/sane.d/dll.d</I> can be freely named. They shall follow the
|
||||
format conventions as apply for <I>dll.conf.</I>
|
||||
|
||||
Note that backends that were pre-loaded when building this library do
|
||||
not have to be listed in this configuration file. That is, if a back‐
|
||||
end was preloaded, then that backend will always be present, regardless
|
||||
|
|
@ -147,7 +153,6 @@
|
|||
<H2>AUTHOR</H2><PRE>
|
||||
David Mosberger
|
||||
|
||||
|
||||
13 Jul 2008 <B><A HREF="sane-dll.5.html">sane-dll(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
|
|
|
|||
|
|
@ -62,12 +62,12 @@
|
|||
|
||||
</PRE>
|
||||
<H2>CONFIGURATION FILE</H2><PRE>
|
||||
The configuration file "/usr/local/etc/sane.d/epjitsu.conf" is used to
|
||||
tell the backend how to look for scanners, and provide options control‐
|
||||
ling the operation of the backend. This file is read each time the
|
||||
frontend asks the backend for a list of scanners, generally only when
|
||||
the frontend starts. If the configuration file is missing, the backend
|
||||
will not work.
|
||||
The configuration file "/etc/sane.d/epjitsu.conf" is used to tell the
|
||||
backend how to look for scanners, and provide options controlling the
|
||||
operation of the backend. This file is read each time the frontend asks
|
||||
the backend for a list of scanners, generally only when the frontend
|
||||
starts. If the configuration file is missing, the backend will not
|
||||
work.
|
||||
|
||||
Scanners can be specified in the configuration file in two ways:
|
||||
|
||||
|
|
|
|||
|
|
@ -20,17 +20,18 @@
|
|||
The <B>sane-fujitsu</B> library implements a SANE (Scanner Access Now Easy)
|
||||
backend which provides access to most Fujitsu flatbed and ADF scanners.
|
||||
|
||||
This document describes backend version 111, which shipped with SANE
|
||||
1.0.23.
|
||||
This document describes backend version 117, which shipped with SANE
|
||||
1.0.24.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>SUPPORTED HARDWARE</H2><PRE>
|
||||
This version supports every known model which speaks the Fujitsu SCSI
|
||||
and SCSI-over-USB protocols. Specifically, the SCSI M309x and M409x
|
||||
series, the SCSI fi-series, most of the USB fi-series, and the USB
|
||||
ScanSnap S5xx/S15xx scanners are supported. Please see the list at
|
||||
http://www.sane-project.org/sane-supported-devices.html for details.
|
||||
series, the SCSI fi-series, most of the USB fi-series, the USB ScanSnap
|
||||
S5xx/S15xx, and the USB iX5xx series scanners are supported. Please see
|
||||
the list at http://www.sane-project.org/sane-supported-devices.html for
|
||||
details.
|
||||
|
||||
This backend may support other Fujitsu scanners. The best way to deter‐
|
||||
mine level of support is to test the scanner directly, or to collect a
|
||||
|
|
@ -170,9 +171,6 @@
|
|||
|
||||
CCITT Fax compression used by older scanners is not supported.
|
||||
|
||||
Hardware automatic paper width detection (aka auto-cropping) is not
|
||||
supported.
|
||||
|
||||
JPEG output is supported by the backend, but not by the SANE protocol,
|
||||
so is disabled in this release. It can be enabled if you rebuild from
|
||||
source.
|
||||
|
|
@ -211,6 +209,10 @@
|
|||
Fujitsu Computer Products of America, Inc.
|
||||
www.fcpa.com
|
||||
|
||||
iX500 support funded by:
|
||||
Prefix Computer Services
|
||||
www.prefixservice.com
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>SEE ALSO</H2><PRE>
|
||||
|
|
@ -218,12 +220,11 @@
|
|||
<B><A HREF="sane-epjitsu.5.html">sane-epjitsu(5)</A></B>
|
||||
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>AUTHOR</H2><PRE>
|
||||
m. allan noah: <kitno455 a t gmail d o t com>
|
||||
|
||||
30 Jan 2011 <B><A HREF="sane-fujitsu.5.html">sane-fujitsu(5)</A></B>
|
||||
17 Sep 2013 <B><A HREF="sane-fujitsu.5.html">sane-fujitsu(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -74,6 +74,16 @@
|
|||
white point. Pixels whith brightness below that value will be
|
||||
scanned as black.
|
||||
|
||||
<B>--brightness</B> <B>value</B>
|
||||
-100..100 (in steps of 1). Set the brightness enhancement.
|
||||
0 for no enhancement, negative values to decrease brigthness,
|
||||
and positive values to increase it.
|
||||
|
||||
<B>--contrast</B> <B>value</B>
|
||||
-100..100 (in steps of 1). Set the contrast enhancement. 0
|
||||
for no enhancement, negative values to decrease contrast, and
|
||||
positive values to increase it.
|
||||
|
||||
<B>--disable-interpolation</B> <B>yes|no</B>
|
||||
When using high resolutions where the horizontal resolu‐
|
||||
tion is smaller than vertical resolution, data is expanded by
|
||||
|
|
@ -94,6 +104,17 @@
|
|||
The lamp will be turned off during the scan. Calibration
|
||||
is still done with lamp on.
|
||||
|
||||
<B>--clear-calibration</B>
|
||||
Clear calibration cache data, triggering a new calibra‐
|
||||
tion for the device when the next scan will happen.
|
||||
|
||||
<B>--calibration-file</B>
|
||||
Specify the calibration file name to use. At least the
|
||||
directory containing the file must exist, since it won't be cre‐
|
||||
ated. This allow to handle the case of several identical devices
|
||||
that would otherwise use the same calibration data. This option
|
||||
is disabled if the backend is ran as root.
|
||||
|
||||
Additionally, several 'software' options are exposed by the backend.
|
||||
These are reimplementations of features provided natively by larger
|
||||
scanners, but running on the host computer. This enables smaller
|
||||
|
|
@ -213,7 +234,6 @@
|
|||
export SANE_DEBUG_GENESYS_GL646=255
|
||||
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>CREDITS</H2><PRE>
|
||||
Jack McGill for donating several sheetfed and flatbed scanners, which
|
||||
|
|
|
|||
|
|
@ -162,7 +162,7 @@
|
|||
<H2>SEE ALSO</H2><PRE>
|
||||
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>, <B><A HREF="sane-artec_eplus48u.5.html">sane-artec_eplus48u(5)</A></B> <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>,
|
||||
<B><A HREF="sane-ma1509.5.html">sane-ma1509(5)</A></B>, <B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(5)</A></B>, <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B>, <B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B>
|
||||
<I>/usr/doc/sane-1.0.22git/gt68xx/gt68xx.CHANGES</I>
|
||||
<I>/usr/doc/sane-1.0.24/gt68xx/gt68xx.CHANGES</I>
|
||||
<I>http://www.meier-geinitz.de/sane/gt68xx</I>
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -70,7 +70,7 @@
|
|||
noises and the scan mechanism may be damaged. Thus, if you hear such a
|
||||
noise, IMMEDIATELY turn off the scanner. This shouldn't happen if your
|
||||
scanner is in the list of known scanners. There is more information in
|
||||
the <I>/usr/doc/sane-1.0.23git/PROBLEMS</I> file.
|
||||
the <I>/usr/doc/sane-1.0.24/PROBLEMS</I> file.
|
||||
|
||||
If you own a Mustek (or Trust) scanner other than the ones listed above
|
||||
that works with this backend, please let us know by sending the scan‐
|
||||
|
|
@ -311,7 +311,7 @@
|
|||
<H2>SEE ALSO</H2><PRE>
|
||||
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B>, <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>, <B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(5)</A></B>,
|
||||
<B><A HREF="sane-gt68xx.5.html">sane-gt68xx(5)</A></B>, <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>, <B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B>
|
||||
<I>/usr/doc/sane-1.0.23git/mustek/mustek.CHANGES</I>
|
||||
<I>/usr/doc/sane-1.0.24/mustek/mustek.CHANGES</I>
|
||||
<I>http://www.meier-geinitz.de/sane/mustek-backend/</I>
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@
|
|||
<HR>
|
||||
<PRE>
|
||||
<!-- Manpage converted by man2html 3.0.1 -->
|
||||
<B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B> <B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B>
|
||||
<B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B> File Formats Manual <B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B>
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
|
|||
|
|
@ -148,8 +148,8 @@
|
|||
<H2>SEE ALSO</H2><PRE>
|
||||
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>, <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B>, <B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B>, <B>sane-plus</B>â€<B>â</B>€<EFBFBD>
|
||||
<B><A HREF="tek.5.html">tek(5)</A></B>, <B><A HREF="sane-gt68xx.5.html">sane-gt68xx(5)</A></B>, <B><A HREF="sane-ma1509.5.html">sane-ma1509(5)</A></B>
|
||||
<I>/usr/doc/sane-1.0.22git/mustek</I><B>_</B><I>usb/mustek</I><B>_</B><I>usb.CHANGES</I>,
|
||||
<I>/usr/doc/sane-1.0.22git/mustek</I><B>_</B><I>usb/mustek</I><B>_</B><I>usb.TODO</I>
|
||||
<I>/usr/doc/sane-1.0.24/mustek</I><B>_</B><I>usb/mustek</I><B>_</B><I>usb.CHANGES</I>,
|
||||
<I>/usr/doc/sane-1.0.24/mustek</I><B>_</B><I>usb/mustek</I><B>_</B><I>usb.TODO</I>
|
||||
<I>http://www.meier-geinitz.de/sane/mustek</I><B>_</B><I>usb-backend/</I>
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -69,7 +69,7 @@
|
|||
<H2>SEE ALSO</H2><PRE>
|
||||
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>, <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>, <B><A HREF="sane-ma1509.5.html">sane-ma1509(5)</A></B>,
|
||||
<B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(5)</A></B>, <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B>, <B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B>
|
||||
<I>/usr/doc/sane-1.0.23git/mustek</I><B>_</B><I>usb2/mustek</I><B>_</B><I>usb2.CHANGES</I>
|
||||
<I>/usr/doc/sane-1.0.24/mustek</I><B>_</B><I>usb2/mustek</I><B>_</B><I>usb2.CHANGES</I>
|
||||
<I>http://www.meier-geinitz.de/sane/mustek</I><B>_</B><I>usb2-backend/</I>
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -12,21 +12,25 @@
|
|||
|
||||
</PRE>
|
||||
<H2>NAME</H2><PRE>
|
||||
<B>sane-pixma</B> - SANE backend for Canon PIXMA Multi-Functions Printers
|
||||
E, MG, MP, MX, ImageCLASS, imageRunner and I-SENSYS series
|
||||
and for Canon CanoScan Flatbed/TPU Scanners
|
||||
sane-pixma - SANE backend for Canon Multi-Function Printers and
|
||||
CanoScan Scanners
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>DESCRIPTION</H2><PRE>
|
||||
The <B>sane-pixma</B> library implements a SANE (Scanner Access Now Easy)
|
||||
backend that provides access to Canon PIXMA multi-function devices
|
||||
(All-in-one printers). The backend implements both USB interface and
|
||||
Network LAN interface using Canon's BJNP protocol. Currently, the folâ€<C3A2>
|
||||
lowing models work with this backend:
|
||||
backend that provides access to Canon PIXMA / i-SENSYS / imageCLASS /
|
||||
imageRUNNER multi-function devices (All-in-one printers) and the Canon
|
||||
CanoScan Flatbed/TPU scanners. The backend implements both USB inter‐
|
||||
face and network interface using Canon's BJNP protocol. The network
|
||||
interface supports scanners over IPv4 as well as IPv6.
|
||||
|
||||
Currently, the following models work with this backend:
|
||||
|
||||
PIXMA MG2100, MG3100, MG4200, MG5100, MG5200, MG5300
|
||||
PIXMA MG6100, MG6200, MG6300, MG8200
|
||||
PIXMA MP140, MP150, MP160, MP170, MP180, MP190
|
||||
PIXMA MP210, MP220, MP240, MP250, MP260, MP270, MP280
|
||||
PIXMA MP210, MP220, MP230, MP240, MP250, MP260, MP270, MP280
|
||||
PIXMA MP360, MP370, MP390
|
||||
PIXMA MP450, MP460, MP470, MP480, MP490
|
||||
PIXMA MP500, MP510, MP520, MP530, MP540, MP550, MP560
|
||||
|
|
@ -34,16 +38,17 @@
|
|||
PIXMA MP700, MP710, MP730, PIXMA MP750 (no grayscale)
|
||||
PIXMA MP800, MP800R, MP810, MP830
|
||||
PIXMA MP960, MP970, MP980, MP990
|
||||
PIXMA MX300, MX310, MX330, MX340, MX350, MX360
|
||||
PIXMA MX300, MX310, MX330, MX340, MX350, MX360, MX370
|
||||
PIXMA MX420, MX700, MX7600
|
||||
PIXMA MX850, MX860, MX870, MX882, MX885
|
||||
ImageCLASS MF3110, MF3240, MF4010, MF4018
|
||||
ImageCLASS MF4120, MF4122, MF4140, MF4150
|
||||
ImageCLASS MF4270, MF4350d, MF4370dn, MF4380dn
|
||||
ImageCLASS MF4410, MF4660, MF4690
|
||||
ImageCLASS MF5770, MF6550, D480
|
||||
I-SENSYS MF4320d, MF4330d
|
||||
CanoScan 8800F, 9000F
|
||||
PIXMA MX850, MX860, MX870, MX882, MX885, MX890
|
||||
imageCLASS MF3110, MF3240, MF4010, MF4018
|
||||
imageCLASS MF4120, MF4122, MF4140, MF4150
|
||||
imageCLASS MF4270, MF4350d, MF4370dn, MF4380dn
|
||||
imageCLASS MF4410, MF4430, MF4660, MF4690, MF4770n
|
||||
imageCLASS MF5730, MF5770, MF6550, D420, D480
|
||||
i-SENSYS MF3010, MF4320d, MF4330d, MF4550d
|
||||
imageRUNNER 1020/1024/1025
|
||||
CanoScan 8800F, 9000F, 9000F Mark II
|
||||
|
||||
The following models are not well tested and/or the scanner sometimes
|
||||
hangs and must be switched off and on.
|
||||
|
|
@ -56,20 +61,15 @@
|
|||
declared in the backend so that they get recognized and activated.
|
||||
Feedback in the sane-devel mailing list welcome.
|
||||
|
||||
PIXMA MG2100, MG3100, MG4100, MG5100, MG5200, MG5300
|
||||
PIXMA MG6100, MG6200, MG8100, MG8200
|
||||
PIXMA E500, E510, E600, E610
|
||||
PIXMA MG2200, MG2400, MG2500, MG3200, MG4100, MG5400, MG5500
|
||||
PIXMA MG6400, MG6500, MG7100, MG8100
|
||||
PIXMA MP375R, MP493, MP495, MP740
|
||||
PIXMA MX320, MX410
|
||||
ImageCLASS MF5630, MF5650, MF5730, MF5750, MF8030, MF8170c
|
||||
imageRunner iR1020, iR1024, iR1025
|
||||
|
||||
The following models may use partly the same Pixma protocol as other
|
||||
devices listed above, but may still need some work. They are declared
|
||||
in the backend as experimental. Snoop logs are required to further
|
||||
investigate, please contact the sane-devel mailing list.
|
||||
|
||||
PIXMA E500, E600
|
||||
PIXMA MX370, MX430, MX510, MX710, MX890
|
||||
PIXMA MX320, MX390, MX410, MX430, MX450, MX510, MX520
|
||||
PIXMA MX710, MX720, MX920
|
||||
imageCLASS MF4570dw, MF5630, MF5650, MF5750, MF8030, MF8170c
|
||||
imageRUNNER 1133
|
||||
i-SENSYS MF5880dn, MF6680dn
|
||||
|
||||
The backend supports:
|
||||
|
||||
|
|
@ -79,7 +79,8 @@
|
|||
els,
|
||||
* a custom gamma table,
|
||||
* Automatic Document Feeder, Simplex and Duplex.
|
||||
* Transparency Unit, 24 or 48 bits depth.
|
||||
* Transparency Unit, 24 or 48 bits depth. Infrared channel on
|
||||
certain models.
|
||||
|
||||
The device name for USB devices is in the form pixma:xxxxyyyy_zzzzz
|
||||
where x, y and z are vendor ID, product ID and serial number respec‐
|
||||
|
|
@ -91,7 +92,7 @@
|
|||
This backend, based on cloning original Canon drivers protocols, is in
|
||||
a production stage. Designed has been carried out without any applica‐
|
||||
ble manufacturer documentation, probably never available. However, we
|
||||
have tested it as well as we could, but it may not work in every situaâ€<C3A2>
|
||||
have tested it as well as we could, but it may not work in all situa‐
|
||||
tions. You will find an up-to-date status at the project homepage. (See
|
||||
below). Users feedback is essential to help improve features and per‐
|
||||
formances.
|
||||
|
|
@ -102,26 +103,56 @@
|
|||
Besides "well-known" options (e.g. resolution, mode etc.) pixma backend
|
||||
also provides the following options for button handling, i.e. the
|
||||
options might change in the future.
|
||||
The button status can be polled i.e. with 'scanimage -A'.
|
||||
Button scan is disabled on MAC OS X due to darwin libusb not handling
|
||||
timeouts in usb interrupt reads.
|
||||
|
||||
<I>button-controlled</I>
|
||||
This option can be used in combination with <B><A HREF="scanadf.1.html">scanadf(1)</A></B> and <B>scan</B>â€<B>â</B>€<EFBFBD>
|
||||
<B><A HREF="image.1.html">image(1)</A></B> in batch mode, for example when you want to scan many
|
||||
photos or multiple-page documents. If it is enabled (i.e. is set
|
||||
to true or yes), the backend waits before every scan until the
|
||||
user presses the "SCAN" button (for MP150) or the color-scan
|
||||
button (for other models). Just put the first page in the scanâ€<C3A2>
|
||||
ner, press the button, then the next page, press the button and
|
||||
so on. When you finished, press the gray-scan button. (For MP150
|
||||
you have to stop the frontend by pressing Ctrl-C for example.)
|
||||
This option can be used by applications (like <B><A HREF="scanadf.1.html">scanadf(1)</A></B> and
|
||||
<B><A HREF="scanimage.1.html">scanimage(1)</A></B>) in batch mode, for example when you want to scan
|
||||
many photos or multiple-page documents. If it is enabled (i.e.
|
||||
is set to true or yes), the backend waits before every scan
|
||||
until the user presses the "SCAN" button (for MP150) or the
|
||||
color-scan button (for other models). Just put the first page in
|
||||
the scanner, press the button, then the next page, press the
|
||||
button and so on. When you finished, press the gray-scan button.
|
||||
(For MP150 you have to stop the frontend by pressing Ctrl-C for
|
||||
example.)
|
||||
|
||||
<I>button-update</I> <I>button-1</I> <I>button-2</I>
|
||||
These options are interesting for developers. To check button
|
||||
status: (1) set <I>button-1</I> and <I>button-2</I> to zero, (2) set <I>button-</I>
|
||||
<I>update</I> (Its type is SANE_TYPE_BUTTON.), (3) get <I>button-1</I> and
|
||||
<I>button-2</I>. If the result is not zero, the corresponding button
|
||||
was pressed.
|
||||
<I>button-update</I>
|
||||
(write only) In the past this option was required to be set to
|
||||
force reading of the button status for <I>button-1</I> and <I>button-2.</I>
|
||||
The <B>sane-pixma</B> no longer requires this option to be used: if no
|
||||
fresh data is available, it will be now requested automatically
|
||||
from the scanner. This option is left for backward compatibility
|
||||
reasons.
|
||||
|
||||
<I>button-1</I> <I>button-2</I>
|
||||
(read only) These options will return the value of the respec‐
|
||||
tive buttons. value 0 means that the button was not pressed, 1
|
||||
is returned when the button was pressed. Some scanners with more
|
||||
than two buttons send the button number as target.
|
||||
|
||||
<I>original</I>
|
||||
(read only) Returns the value of the type or size of original to
|
||||
be scanned if the scanner provides that data. Known values of
|
||||
type: 1 = document, 2 = foto, 5 = film. Known values of size: 1
|
||||
= A4, 2 = Letter, 8 = 10x15, 9 = 13x18, b = auto. Not all scan‐
|
||||
ners can provide this data.
|
||||
|
||||
<I>target</I> (read only) Returns the value of the target of the scan opera‐
|
||||
tion if the scanner provides that data. The values depend on the
|
||||
scanner type. Known values: 1 = save to disk, 2 = save to pdf, 3
|
||||
= send to email, 4 = send to application or 1 = JPEG, 2 = TIFF,
|
||||
3 = PDF, 4 = Compact PDF. For some scanners this value is equiv‐
|
||||
alent to the number of the pressed button. Not all scanners can
|
||||
provide this data.
|
||||
|
||||
<I>scan-resolution</I>
|
||||
(read only) Returns the resolution of the scan operation if the
|
||||
scanner provides that data. Known values: 1 = 75 dpi, 2 = 150
|
||||
dpi, 3 = 300 dpi, 4 = 600 dpi. Not all scanners can provide this
|
||||
data.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -144,8 +175,10 @@
|
|||
|
||||
<I>bjnp://<host></I>
|
||||
where host is the hostname or IP address of the scanner, e.g.
|
||||
bjnp://10.0.1.4 or bjnp://myscanner.mydomain.org. Define each
|
||||
scanner on a new line.
|
||||
bjnp://10.0.1.4 for IPv4,
|
||||
bjnp://[2001:888:118e:18e2:21e:8fff:fe36:b64a] for a literal
|
||||
IPv6-address or bjnp://myscanner.mydomain.org. Define each scan‐
|
||||
ner on a new line.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -156,9 +189,11 @@
|
|||
</PRE>
|
||||
<H2>NETWORKING SUPPORT</H2><PRE>
|
||||
The pixma backend supports network scanners using the so called Canon
|
||||
BJNP protocol. Configuration is normally not required. The pixma
|
||||
backend will auto-detect your scanner if it is within the same subnet
|
||||
as your computer if your OS does support this.
|
||||
BJNP protocol. Both IPv4 and IPv6 are supported.
|
||||
|
||||
Configuration is normally not required. The pixma backend will auto-
|
||||
detect your scanner if it is within the same subnet as your computer if
|
||||
your OS does support this.
|
||||
|
||||
If your scanner can not be auto-detected, you can add it to the pixma
|
||||
configuration file (see above).
|
||||
|
|
@ -172,14 +207,16 @@
|
|||
|
||||
Scanner detection is slightly more complicated. The pixma backend sends
|
||||
a broadcast on all direct connected subnets it can find (provided your
|
||||
OS allows for enumeration of all interfaces). The broadcast is sent
|
||||
FROM port 8612 TO port 8612 on the broadcast address of each interface.
|
||||
The outgoing packets will be allowed by the rule described above.
|
||||
OS allows for enumeration of all netowrk interfaces). The broadcast is
|
||||
sent FROM port 8612 TO port 8612 on the broadcast address of each
|
||||
interface. The outgoing packets will be allowed by the rule described
|
||||
above.
|
||||
|
||||
Responses from the scanner are sent back to the computer TO port 8612.
|
||||
Connection tracking however does not see a match as the response does
|
||||
not come from the broadcast address but from the scanners own address.
|
||||
You will therefore have to allow incoming packets TO port 8612 on your
|
||||
computer.
|
||||
For automatic detection of your scanner, you will therefore have to
|
||||
allow incoming packets TO port 8612 on your computer.
|
||||
|
||||
So in short: open the firewall for all traffic from your computer to
|
||||
port 8612 AND to port 8612 to your computer.
|
||||
|
|
@ -193,15 +230,27 @@
|
|||
<H2>ENVIRONMENT</H2><PRE>
|
||||
<B>SANE_DEBUG_PIXMA</B>
|
||||
If the library was compiled with debug support enabled, this
|
||||
environment variable controls the debug level for this backend.
|
||||
Higher value increases the verbosity.
|
||||
|
||||
environment variable controls the debug level for this backend
|
||||
itself. Higher value increases the verbosity and includes the
|
||||
information printed at the lower levels.
|
||||
0 print nothing (default)
|
||||
1 print error and warning messages (recommended)
|
||||
2 print informational messages
|
||||
3 print debug-level messages
|
||||
11 dump USB/BJNP traffics
|
||||
21 full dump USB/BJNP traffic
|
||||
11 dump USB traffic
|
||||
21 full dump USB traffic
|
||||
|
||||
<B>SANE_DEBUG_BJNP</B>
|
||||
If the library was compiled with debug support enabled, this
|
||||
environment variable controls the debug level for the <B>BJNP</B> net‐
|
||||
work protocol for this backend. Higher value increases the ver‐
|
||||
bosity and includes the information printed at the lower levels.
|
||||
0 print nothing (default)
|
||||
1 Print error and warning messages (recommended)
|
||||
2 Print high level function tracing information
|
||||
3 Print more detailed protocol tracing information
|
||||
4 Print protocol headers
|
||||
5 Print full protocol contents
|
||||
|
||||
<B>PIXMA_EXPERIMENT</B>
|
||||
Setting to a non-zero value will enable the support for experi‐
|
||||
|
|
@ -243,7 +292,7 @@
|
|||
not be able to write subdrivers for models we don't have. See also the
|
||||
project homepage.
|
||||
|
||||
31 Jul 2012 <B><A HREF="sane-pixma.5.html">sane-pixma(5)</A></B>
|
||||
24 Sep 2013 <B><A HREF="sane-pixma.5.html">sane-pixma(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -117,6 +117,7 @@
|
|||
USB Model: ASIC: Properties: Prod-ID
|
||||
----------------------------------------------------------
|
||||
Q-Scan USB001 LM9832 300x600dpi 42bit 512Kb 0x1000
|
||||
Q-Scan USB201 LM9832 300x600dpi 42bit 512Kb 0x2000
|
||||
|
||||
Vendor Visioneer - ID: 0x04A7
|
||||
----------------------------------------------------------
|
||||
|
|
@ -309,7 +310,7 @@
|
|||
</PRE>
|
||||
<H2>SEE ALSO</H2><PRE>
|
||||
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>, <B><A HREF="sane-u12.5.html">sane-u12(5)</A></B>, <B><A HREF="sane-gt68xx.5.html">sane-gt68xx(5)</A></B>,
|
||||
<I>/usr/doc/sane-1.0.22git/plustek/Plustek-USB.changes</I>
|
||||
<I>/usr/doc/sane-1.0.24/plustek/Plustek-USB.changes</I>
|
||||
<I>http://www.gjaeger.de/scanner/plustek/</I>
|
||||
|
||||
|
||||
|
|
@ -353,7 +354,7 @@
|
|||
|
||||
* Negative/Slide scanning quality is poor.
|
||||
|
||||
25 Aug 2008 <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>
|
||||
13 Feb 2013 <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>
|
||||
</PRE>
|
||||
<HR>
|
||||
<ADDRESS>
|
||||
|
|
|
|||
|
|
@ -342,7 +342,7 @@
|
|||
</PRE>
|
||||
<H2>SEE ALSO</H2><PRE>
|
||||
<B><A HREF="sane.7.html">sane(7)</A></B>,
|
||||
<I>/usr/doc/sane-1.0.23git/plustek/Plustek-PARPORT.changes</I>
|
||||
<I>/usr/doc/sane-1.0.24/plustek/Plustek-PARPORT.changes</I>
|
||||
<I>http://www.gjaeger.de/scanner/plustek</I><B>_</B><I>pp/</I>
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -127,7 +127,7 @@
|
|||
</PRE>
|
||||
<H2>SEE ALSO</H2><PRE>
|
||||
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>, <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>,
|
||||
<I>/usr/doc/sane-1.0.23git/u12/U12.changes</I>
|
||||
<I>/usr/doc/sane-1.0.24/u12/U12.changes</I>
|
||||
<I>http://www.gjaeger.de/scanner/u12/</I>
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -84,8 +84,8 @@
|
|||
which support dynamic setting of access permissions. SANE comes with
|
||||
udev and hotplug scripts in the directory tools/udev and tools/hotplug.
|
||||
They can be used for setting permissions, see
|
||||
/usr/doc/sane-1.0.23git/README.linux, tools/README and the README in
|
||||
the tools/hotplug directory for more details.
|
||||
/usr/doc/sane-1.0.24/README.linux, tools/README and the README in the
|
||||
tools/hotplug directory for more details.
|
||||
|
||||
For the <B>BSDs</B>, the device files used by libusb are named <I>/dev/ugen*</I>.
|
||||
Use chmod to apply appropriate permissions.
|
||||
|
|
|
|||
|
|
@ -58,10 +58,9 @@
|
|||
information about several aspects of <B>SANE.</B> A name with a number in
|
||||
parenthesis (e.g. `<B><A HREF="sane-dll.5.html">sane-dll(5)</A></B>') points to a manual page. In this case
|
||||
`<B>man</B> <B>5</B> <B>sane-dll</B>' will display the page. Entries like
|
||||
`<I>/usr/local/doc/sane-1.0.23git/sane.tex</I>' are references to text files
|
||||
that were copied to the <B>SANE</B> documentation directory
|
||||
(<I>/usr/local/doc/sane-1.0.23git/</I>) during installation. Everything else
|
||||
is a URL to a resource on the web.
|
||||
`<I>/usr/doc/sane-1.0.24/sane.tex</I>' are references to text files that were
|
||||
copied to the <B>SANE</B> documentation directory (<I>/usr/doc/sane-1.0.24/</I>) dur‐
|
||||
ing installation. Everything else is a URL to a resource on the web.
|
||||
|
||||
<B>SANE</B> <B>homepage</B>
|
||||
Information on all aspects of SANE including a tutorial and a link to
|
||||
|
|
@ -75,7 +74,7 @@
|
|||
CAN YOU HELP SANE for details. There are lists for specific releases
|
||||
of SANE, for the current development version and a search engine:
|
||||
<I>http://www.sane-project.org/sane-supported-devices.html</I>. The lists
|
||||
are also installed on your system at /usr/local/doc/sane-1.0.23git/.
|
||||
are also installed on your system at /usr/doc/sane-1.0.24/.
|
||||
|
||||
<B>SANE</B> <B>mailing</B> <B>list</B>
|
||||
There is a mailing list for the purpose of discussing the SANE stan‐
|
||||
|
|
@ -95,8 +94,8 @@
|
|||
server, etc.).
|
||||
|
||||
<B>Compiling</B> <B>and</B> <B>installing</B> <B>SANE</B>
|
||||
Look at <I>/usr/local/doc/sane-1.0.23git/README</I> and the os-dependent
|
||||
README files for information about compiling and installing <B>SANE.</B>
|
||||
Look at <I>/usr/doc/sane-1.0.24/README</I> and the os-dependent README files
|
||||
for information about compiling and installing <B>SANE.</B>
|
||||
|
||||
<B>SCSI</B> <B>configuration</B>
|
||||
For information about various systems and SCSI controllers see
|
||||
|
|
@ -415,7 +414,7 @@
|
|||
|
||||
Also, have a look at the backend information page at
|
||||
<I>http://www.sane-project.org/sane-supported-devices.html</I> and the list of
|
||||
projects in <I>/usr/local/doc/sane-1.0.23git/PROJECTS</I>.
|
||||
projects in <I>/usr/doc/sane-1.0.24/PROJECTS</I>.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -449,7 +448,7 @@
|
|||
|
||||
Also, have a look at the backend information page at
|
||||
<I>http://www.sane-project.org/sane-supported-devices.html</I> and the list of
|
||||
projects in <I>/usr/local/doc/sane-1.0.23git/PROJECTS</I>.
|
||||
projects in <I>/usr/doc/sane-1.0.24/PROJECTS</I>.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -486,7 +485,7 @@
|
|||
|
||||
Also, have a look at the backend information page at
|
||||
<I>http://www.sane-project.org/sane-supported-devices.html</I> and the list of
|
||||
projects in <I>/usr/local/doc/sane-1.0.23git/PROJECTS</I>.
|
||||
projects in <I>/usr/doc/sane-1.0.24/PROJECTS</I>.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -495,7 +494,7 @@
|
|||
<B>sane-dll</B> meta backend. If you have any questions about the dynamic
|
||||
loading, read <B><A HREF="sane-dll.5.html">sane-dll(5)</A></B>. <B>SANE</B> frontend can also be linked to other
|
||||
backends directly by copying or linking a backend to <B>libsane.so</B> in
|
||||
<I>/usr/local/lib/sane</I>.
|
||||
<I>/usr/lib/sane</I>.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -507,19 +506,18 @@
|
|||
|
||||
The <B>SANE</B> standard defines the application programming interface (API)
|
||||
that is used to communicate between frontends and backends. It can be
|
||||
found at <I>/usr/local/doc/sane-1.0.23git/sane.ps</I> (if latex is installed
|
||||
on your system) and on the <B>SANE</B> website:
|
||||
<I>http://www.sane-project.org/html/</I> (HTML), or
|
||||
<I>http://www.sane-project.org/sane.ps</I> (Postscript).
|
||||
found at <I>/usr/doc/sane-1.0.24/sane.ps</I> (if latex is installed on your
|
||||
system) and on the <B>SANE</B> website: <I>http://www.sane-project.org/html/</I>
|
||||
(HTML), or <I>http://www.sane-project.org/sane.ps</I> (Postscript).
|
||||
|
||||
There is some more information for programmers in
|
||||
<I>/usr/local/doc/sane-1.0.23git/backend-writing.txt</I>. Most of the interâ€<C3A2>
|
||||
nal <B>SANE</B> routines (<B>sanei</B>) are documented using doxygen:
|
||||
<I>/usr/doc/sane-1.0.24/backend-writing.txt</I>. Most of the internal <B>SANE</B>
|
||||
routines (<B>sanei</B>) are documented using doxygen:
|
||||
<I>http://www.sane-project.org/sanei/</I>. Before a new backend or frontend
|
||||
project is started, have a look at
|
||||
<I>/usr/local/doc/sane-1.0.23git/PROJECTS</I> for projects that are planned or
|
||||
not yet included into the <B>SANE</B> distribution and at our bug-tracking
|
||||
system: <I>http://www.http://www.sane-project.org/bugs.html</I>.
|
||||
project is started, have a look at <I>/usr/doc/sane-1.0.24/PROJECTS</I> for
|
||||
projects that are planned or not yet included into the <B>SANE</B> distribu‐
|
||||
tion and at our bug-tracking system:
|
||||
<I>http://www.http://www.sane-project.org/bugs.html</I>.
|
||||
|
||||
There are some links on how to find out about the protocol of a scan‐
|
||||
ner: <I>http://www.meier-geinitz.de/sane/misc/develop.html</I>.
|
||||
|
|
@ -531,17 +529,17 @@
|
|||
|
||||
</PRE>
|
||||
<H2>FILES</H2><PRE>
|
||||
<I>/usr/local/etc/sane.d/*.conf</I>
|
||||
<I>/etc/sane.d/*.conf</I>
|
||||
The backend configuration files.
|
||||
|
||||
<I>/usr/local/lib/sane/libsane-*.a</I>
|
||||
<I>/usr/lib/sane/libsane-*.a</I>
|
||||
The static libraries implementing the backends.
|
||||
|
||||
<I>/usr/local/lib/sane/libsane-*.so</I>
|
||||
<I>/usr/lib/sane/libsane-*.so</I>
|
||||
The shared libraries implementing the backends (present on sys‐
|
||||
tems that support dynamic loading).
|
||||
|
||||
<I>/usr/local/doc/sane-1.0.23git/*</I>
|
||||
<I>/usr/doc/sane-1.0.24/*</I>
|
||||
<B>SANE</B> documentation: The standard, READMEs, text files for back‐
|
||||
ends etc.
|
||||
|
||||
|
|
@ -562,14 +560,14 @@
|
|||
|
||||
Now your scanner is detected by the operating system but not by <B>SANE</B>?
|
||||
Try <B>scanimage</B> <B>-L</B>. If the scanner is not found, check that the back‐
|
||||
end's name is mentioned in <I>/usr/local/etc/sane.d/dll.conf</I>. Some backâ€<C3A2>
|
||||
ends are commented out by default. Remove the comment sign for your
|
||||
backend in this case. Also some backends aren't compiled at all if one
|
||||
of their prerequisites are missing. Examples include dc210, dc240,
|
||||
canon_pp, hpsj5s, gphoto2, pint, qcam, v4l, net, sm3600, snapscan, pnm.
|
||||
If you need one of these backends and they aren't available, read the
|
||||
build instructions in the <B>README</B> file and the individual manual pages
|
||||
of the backends.
|
||||
end's name is mentioned in <I>/etc/sane.d/dll.conf</I>. Some backends are
|
||||
commented out by default. Remove the comment sign for your backend in
|
||||
this case. Also some backends aren't compiled at all if one of their
|
||||
prerequisites are missing. Examples include dc210, dc240, canon_pp,
|
||||
hpsj5s, gphoto2, pint, qcam, v4l, net, sm3600, snapscan, pnm. If you
|
||||
need one of these backends and they aren't available, read the build
|
||||
instructions in the <B>README</B> file and the individual manual pages of the
|
||||
backends.
|
||||
|
||||
Another reason for not being detected by <B>scanimage</B> <B>-L</B> may be a missing
|
||||
or wrong configuration in the backend's configuration file. While <B>SANE</B>
|
||||
|
|
@ -631,10 +629,10 @@
|
|||
For reporting bugs or requesting new features, please use our bug-
|
||||
tracking system: <I>http://www.sane-project.org/bugs.html</I>. You can also
|
||||
contact the author of your backend directly. Usually the email address
|
||||
can be found in the <I>/usr/local/doc/sane-1.0.23git/AUTHORS</I> file or the
|
||||
backend's manpage. For general discussion about SANE, please use the
|
||||
<B>SANE</B> mailing list sane-devel (see <I>http://www.sane-project.org/mailâ</I>€<EFBFBD>
|
||||
<I>ing-lists.html</I> for details).
|
||||
can be found in the <I>/usr/doc/sane-1.0.24/AUTHORS</I> file or the backend's
|
||||
manpage. For general discussion about SANE, please use the <B>SANE</B> mailing
|
||||
list sane-devel (see <I>http://www.sane-project.org/mailing-lists.html</I> for
|
||||
details).
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -664,9 +662,9 @@
|
|||
</PRE>
|
||||
<H2>AUTHOR</H2><PRE>
|
||||
David Mosberger-Tang and many many more (see
|
||||
<I>/usr/local/doc/sane-1.0.23git/AUTHORS</I> for details). This man page was
|
||||
written by Henning Meier-Geinitz. Quite a lot of text was taken from
|
||||
the <B>SANE</B> standard, several man pages, and README files.
|
||||
<I>/usr/doc/sane-1.0.24/AUTHORS</I> for details). This man page was written
|
||||
by Henning Meier-Geinitz. Quite a lot of text was taken from the <B>SANE</B>
|
||||
standard, several man pages, and README files.
|
||||
|
||||
14 Jul 2008 <B><A HREF="sane.7.html">sane(7)</A></B>
|
||||
</PRE>
|
||||
|
|
|
|||
116
man/saned.8.html
116
man/saned.8.html
|
|
@ -17,7 +17,7 @@
|
|||
|
||||
</PRE>
|
||||
<H2>SYNOPSIS</H2><PRE>
|
||||
<B>saned</B> <B>[</B> <B>-a</B> <I>[</I> <I>username</I> <I>]</I> <B>|</B> <B>-d</B> <I>[</I> <I>n</I> <I>]</I> <B>|</B> <B>-s</B> <I>[</I> <I>n</I> <I>]</I> <B>]</B>
|
||||
<B>saned</B> <B>[</B> <B>-a</B> <I>[</I> <I>username</I> <I>]</I> <B>|</B> <B>-d</B> <I>[</I> <I>n</I> <I>]</I> <B>|</B> <B>-s</B> <I>[</I> <I>n</I> <I>]</I> <B>|</B> <B>-h</B> <B>]</B>
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -36,15 +36,17 @@
|
|||
<B>-a</B> , <B>saned</B> will drop root privileges and run as this user (and group).
|
||||
|
||||
The <B>-d</B> and <B>-s</B> flags request that <B>saned</B> run in debug mode (as opposed to
|
||||
<B><A HREF="inetd.8.html">inetd(8)</A></B> mode). In this mode, <B>saned</B> explicitly waits for a connection
|
||||
request. When compiled with debugging enabled, these flags may be fol‐
|
||||
lowed by a number to request debug info. The larger the number, the
|
||||
more verbose the debug output. E.g., <B>-d128</B> will request printing of
|
||||
all debug info. Debug level 0 means no debug output at all. The default
|
||||
value is 2. If flag <B>-d</B> is used, the debug messages will be printed to
|
||||
stderr while <B>-s</B> requests using syslog.
|
||||
<B><A HREF="inetd.8.html">inetd(8)</A></B> daemon mode). In this mode, <B>saned</B> explicitly waits for a conâ€<EFBFBD>
|
||||
nection request. When compiled with debugging enabled, these flags may
|
||||
be followed by a number to request debug info. The larger the number,
|
||||
the more verbose the debug output. E.g., <B>-d128</B> will request printing
|
||||
of all debug info. Debug level 0 means no debug output at all. The
|
||||
default value is 2. If flag <B>-d</B> is used, the debug messages will be
|
||||
printed to stderr while <B>-s</B> requests using syslog.
|
||||
|
||||
If <B>saned</B> is run from inetd or xinetd, no option can be given.
|
||||
If <B>saned</B> is run from inetd, xinetd or systemd, no option can be given.
|
||||
|
||||
The <B>-h</B> flag displays a short help message.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
@ -93,33 +95,53 @@
|
|||
|
||||
|
||||
</PRE>
|
||||
<H2>INETD CONFIGURATION</H2><PRE>
|
||||
<H2>SERVER DAEMON CONFIGURATION</H2><PRE>
|
||||
For <B>saned</B> to work properly in its default mode of operation, it is also
|
||||
necessary to add a configuration line to <I>/etc/inetd.conf</I>. Note that
|
||||
your inetd must support IPv6 if you want to connect to saned over IPv6
|
||||
; xinetd and openbsd-inetd are known to support IPv6, check the docu‐
|
||||
mentation for your inetd daemon.
|
||||
necessary to add the appropriate configuration for <I>(x)inetd</I> <I>or</I> <I>systemd.</I>
|
||||
(see below). Note that your inetd must support IPv6 if you want to
|
||||
connect to saned over IPv6 ; xinetd, openbsd-inetd and systemd are
|
||||
known to support IPv6, check the documentation for your inetd daemon.
|
||||
|
||||
In the sections below the configuration for <I>inetd,</I> <I>xinetd</I> and <I>systemd</I>
|
||||
are described in more detail.
|
||||
|
||||
For the configurations below it is necessary to add a line of the folâ€<C3A2>
|
||||
lowing form to <I>/etc/services</I>:
|
||||
|
||||
sane-port 6566/tcp # SANE network scanner daemon
|
||||
|
||||
The official IANA short name for port 6566 is "sane-port". The older
|
||||
name "sane" is now deprecated.
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>INETD CONFIGURATION</H2><PRE>
|
||||
It is required to add a single line to the inetd configuration file
|
||||
<I>(/etc/inetd.conf)</I>
|
||||
|
||||
The configuration line normally looks like this:
|
||||
|
||||
sane-port stream tcp nowait saned.saned /usr/sbin/saned saned
|
||||
|
||||
However, if your system uses <B><A HREF="tcpd.8.html">tcpd(8)</A></B> for additional security screening,
|
||||
you may want to disable saned access control by putting ``+'' in
|
||||
<I>saned.conf</I> and use a line of the following form in <I>/etc/inetd.conf</I>
|
||||
instead:
|
||||
However, if your system uses <B><A HREF="tcpd.8.html">tcpd(8)</A></B> for additional security
|
||||
screening, you may want to disable saned access control by
|
||||
putting ``+'' in <I>saned.conf</I> and use a line of the following form
|
||||
in <I>/etc/inetd.conf</I> instead:
|
||||
|
||||
sane-port stream tcp nowait saned.saned /usr/sbin/tcpd
|
||||
/usr/sbin/saned
|
||||
|
||||
Note that both examples assume that there is a <B>saned</B> group and a <B>saned</B>
|
||||
user. If you follow this example, please make sure that the access
|
||||
permissions on the special device are set such that <B>saned</B> can access
|
||||
the scanner (the program generally needs read and write access to scan‐
|
||||
ner devices).
|
||||
Note that both examples assume that there is a <B>saned</B> group and a
|
||||
<B>saned</B> user. If you follow this example, please make sure that
|
||||
the access permissions on the special device are set such that
|
||||
<B>saned</B> can access the scanner (the program generally needs read
|
||||
and write access to scanner devices).
|
||||
|
||||
|
||||
</PRE>
|
||||
<H2>XINETD CONFIGURATION</H2><PRE>
|
||||
If xinetd is installed on your system instead of inetd the following
|
||||
example for xinetd.conf may be helpful:
|
||||
example for <I>/etc/xinetd.conf</I> may be helpful:
|
||||
|
||||
# default: off
|
||||
# description: The sane server accepts requests
|
||||
|
|
@ -135,13 +157,49 @@
|
|||
server = /usr/sbin/saned
|
||||
}
|
||||
|
||||
Finally, it is also necessary to add a line of the following form to
|
||||
<I>/etc/services</I>:
|
||||
|
||||
sane-port 6566/tcp # SANE network scanner daemon
|
||||
</PRE>
|
||||
<H2>SYSTEMD CONFIGURATION</H2><PRE>
|
||||
for systemd we need to add 2 configuation files in <I>/etc/systemd/system.</I>
|
||||
|
||||
The official IANA short name for port 6566 is "sane-port". The older
|
||||
name "sane" is now deprecated.
|
||||
The first file we need to add here is called <I>saned.socket.</I> It shall
|
||||
have the following contents:
|
||||
|
||||
[Unit]
|
||||
Description=saned incoming socket
|
||||
|
||||
[Socket]
|
||||
ListenStream=6566
|
||||
Accept=yes
|
||||
MaxConnections=1
|
||||
|
||||
[Install]
|
||||
WantedBy=sockets.target
|
||||
|
||||
The second file to be added is <I>saned@.service</I> with the following conâ€<C3A2>
|
||||
tents:
|
||||
|
||||
[Unit]
|
||||
Description=Scanner Service
|
||||
Requires=saned.socket
|
||||
|
||||
[Service]
|
||||
ExecStart=/usr/sbin/saned
|
||||
User=saned
|
||||
Group=saned
|
||||
StandardInput=null
|
||||
StandardOutput=syslog
|
||||
StandardError=syslog
|
||||
# Environment=SANE_CONFIG_DIR=/etc/sane.d SANE_DEBUG_DLL=255
|
||||
|
||||
Is you need to set an environment variable for saned like <B>SANE_CON</B>â€<B>â</B>€<EFBFBD>
|
||||
<B>FIG_DIR</B> you will have to remove the # on the last line and set the
|
||||
variable appropriately. Multiple variables can be set by separating
|
||||
the assignments by spaces as shown in the example above.
|
||||
|
||||
Unlike <I>(x)inetd</I> systemd allows debugging output from backends set using
|
||||
<B>SANE_DEBUG_<backend_name></B> to be captured. With the service unit as
|
||||
described above, the debugging output is forwarded to the system log.
|
||||
|
||||
|
||||
</PRE>
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@
|
|||
<H2>SYNOPSIS</H2><PRE>
|
||||
<B>scanimage</B> [<B>-d</B>|<B>--device-name</B> <I>dev</I>] [<B>--format</B> <I>format</I>] [<B>-i</B>|<B>--icc-profile</B>
|
||||
<I>profile</I>] [<B>-L</B>|<B>--list-devices</B>] [<B>-f</B>|<B>--formatted-device-list</B> <I>format</I>]
|
||||
[<B>--batch</B> [=<I>format</I>]] [<B>--batch-start</B> <I>start</I>] [<B>--batch-count</B> <I>count</I>]
|
||||
[<B>-b</B>|<B>--batch</B> [=<I>format</I>]] [<B>--batch-start</B> <I>start</I>] [<B>--batch-count</B> <I>count</I>]
|
||||
[<B>--batch-increment</B> <I>increment</I>] [<B>--batch-double</B>] [<B>--accept-md5-only</B>]
|
||||
[<B>-p</B>|<B>--progress</B>] [<B>-n</B>|<B>--dont-scan</B>] [<B>-T</B>|<B>--test</B>] [<B>-A</B>|<B>--all-options</B>]
|
||||
[<B>-h</B>|<B>--help</B>] [<B>-v</B>|<B>--verbose</B>] [<B>-B</B>|<B>--buffer-size</B> [=<I>size</I>]] [<B>-V</B>|<B>--version</B>]
|
||||
|
|
|
|||
Plik diff jest za duży
Load Diff
Plik diff jest za duży
Load Diff
|
|
@ -12,6 +12,7 @@ a0cfdfdebca2feb4f2ba5d3418b15a42 sane-backends-1.0.20.tar.gz
|
|||
be586a23633949cf2ecf0c9c6d769130 sane-backends-1.0.21.tar.gz
|
||||
fadf56a60f4776bfb24491f66b617cf5 sane-backends-1.0.22.tar.gz
|
||||
e226a89c54173efea80e91e9a5eb6573 sane-backends-1.0.23.tar.gz
|
||||
1ca68e536cd7c1852322822f5f6ac3a4 sane-backends-1.0.24.tar.gz
|
||||
a7de89c3e67495e8a38ca63b2ff693c4 sane-frontends-1.0.10.tar.gz
|
||||
59b143e12c926726db16983d288aa1a1 sane-frontends-1.0.11.tar.gz
|
||||
6a6166428491b268f5ebe03f16d1bc1f sane-frontends-1.0.12.tar.gz
|
||||
|
|
|
|||
1881
sane-mfgs.html
1881
sane-mfgs.html
Plik diff jest za duży
Load Diff
|
|
@ -104,6 +104,7 @@
|
|||
</p>
|
||||
<p>
|
||||
SANE version:
|
||||
<a href="sane-backends-1.0.23.html">1.0.23</a>,
|
||||
<a href="sane-backends-1.0.22.html">1.0.22</a>,
|
||||
<a href="sane-backends-1.0.21.html">1.0.21</a>,
|
||||
<a href="sane-backends-1.0.20.html">1.0.20</a>,
|
||||
|
|
|
|||
Ładowanie…
Reference in New Issue