Never used ethernet accessible scanners, but a
good practice on using sane from sources is to
be sure you don't have the previous versions'
'leftovers' (configs, `rules.d` files, ...) in
your installation.
I'd say your log hints at saned already being
run on your system with some already existing
(or default) configs.
What does `netstat -t -na` say?
-Yury
On 05/05/16 03:10, Gene Heskett wrote:
...
Back on topic, it seems I cannot run saned as a background daemon,
but I can't find where its disabled. I found a debug log that
apparently is being generated by saned, and here are the results of
the last attempt to start it:
===========================
May 4 00:53:43 coyote saned[21234]: saned (AF-indep+IPv6) from
sane-backends 1.0.22 starting up May 4 00:53:43 coyote
saned[21234]: do_bindings: [1] bind failed: Address already in use
May 4 00:53:43 coyote saned[21234]: do_bindings: [0] bind failed:
Address already in use May 4 00:53:43 coyote saned[21234]:
do_bindings: couldn't bind an address. Exiting. May 4 00:53:43
coyote saned[21234]: FATAL ERROR; bailing out, waiting for
children... May 4 00:53:43 coyote saned[21234]: bail_out: all
children exited ============================
So thats a very non-informative log. :( How do I make it tell me
what addresses fail?
...
--
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
to sane-devel-requ...@lists.alioth.debian.org
