[sane-devel] more detailed saned problem

Henning Meier-Geinitz henning@meier-geinitz.de
Sun, 28 Oct 2001 16:34:02 +0100


On Sun, Oct 28, 2001 at 10:29:36PM +0800, Ka Chun, Cheng wrote:
> hi there, I posted eariler, and now I'm knowing more of my problem...
> I'm using redhat 7.1, sane RPMs uninstalled, installed sane 1.0.5
> backend and frontend from source I successed once but after reboot it
> all fail except saned -d from prompt.

Why do you use the "saned -d" trick? Doesn't it work with running
saned by xinetd?

> 4:ren \usr\local\sbin\saned to saned.bin

What happens if you don't do this and just use the saned binary?

> #!/bin/sh
> cd /tmp
> #exec /usr/local/sbin/saned.bin 2>saned.$$.stderror | tee saned.$$.stdout
> #exec /usr/local/sbin/saned.bin
> exec /usr/local/sbin/saned.bin -d
> the first exec one give me empty log file(saned.????.stdout),

In principle, this should work. Try to remove the "| tee ...", this
works for me. On stdout, there should only be the data flow over the

> the second and the third are the same.

The second one should work, but no log will be created.

> give me no log file,
> windows scanimage say scanimage: no SANE devices found

The third one can't work, because -d tries to listen on the SANE port
which is occupied bei xinetd.

> /var/log/messages say
> access by kccheng@rex accepted
> exiting

This usually means everything is ok.

When your saned is installed correctly you should be able to see your
scanner with scanimage -L on your Linux computer twice. Once directly
and once via net:localhost. You must uncomment "localhost" in net.conf
for this test.

> tried to change hosts.allow, added the line. no difference.
> #
> # hosts.allow This file describes the names of the hosts which are
> #  allowed to use the local INET services, as decided
> #  by the '/usr/sbin/tcpd' server.
> #
> ALL:

Doesn't help for saned if tcpwrappers aren't used.
> it looks strange, as /var/log/messages say ACCEPTED!, and it was
> working before I reboot.

If it's accepted, it should work. I don't know what's going wrong here.