Q: saned works on one box , but does not work on another , same conf´s

Peter Schroeder (p.l.schroeder@gmx.de)
Fri, 14 May 1999 21:19:01 +0200

Hi ,

I´ve installed sane on two Linux boxes, on both I´ve configured
net and saned, but it works only on one of them.

Here is what scanimage -L produces (no scanners, just virtual pnm things):

Box A: ("workbox"):
device `pnm:0' is a Noname PNM file reader virtual device
device `pnm:1' is a Noname PNM file reader virtual device
device `net:localhost:pnm:0' is a Noname PNM file reader virtual device
device `net:localhost:pnm:1' is a Noname PNM file reader virtual device

Box B: ("commbox")
device `pnm:0' is a Noname PNM file reader virtual device
device `pnm:1' is a Noname PNM file reader virtual device
device `net:workbox.privat.de:pnm:0' is a Noname PNM file reader virtual device
device `net:workbox.privat.de:pnm:1' is a Noname PNM file reader virtual device

It seems that the net backend works fine on both boxes,
whereas saned works well only on workbox, but does not on commbox.
I am clueless, even stopping inetd and releasing saned -d128 has not given any
clues:
On both boxes same reaction: saned -d terminates after the scanimage -L is
released. No further output of saned, but scanImage produces same output as
mentioned above.

Of course I´ve checked saned.conf billions of times ,
saned.conf on worbox mentions localhost and commbox,
saned.conf on commbox mentions localhost and workbox.

Ideas?

--
--------------------------
Dr. Peter Ludwig Schroeder
p.l.schroeder@gmx.de
--------------------------

--
Source code, list archive, and docs: http://www.mostang.com/sane/
To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com