SANE and saned

Ian Grant (I.A.N.Grant@damtp.cam.ac.uk)
Mon, 13 Jul 1998 15:09:47 +0100 (BST)

I'm running a tcp-wrappered saned on a linux box and accessing it from
Digital Unix machines and Intel Linux machines across the network. It
works well, except I don't understand how the saned.conf file works. I
have no saned.conf file anywhere and saned seems to talk to anyone the tcp
wrappers let through. As it happens this suits me fine: I didn't want to
have to explicitly list all 100-odd hosts on our network. But I expected,
from the description in the saned man page, that I would have to do this.
What are the circumstances in which saned.conf is used?

Also, the saned man page claims that saned and the net backend use service
'sane' when in fact they look for 'saned'. Most of the time this is not a
problem, because when they fail to find saned listed in /etc/services they
silently fall back to the default service number 6566. If one wants to
change the service number from the default though, it won't work, because
the programs will still fall back to 6566.

Apart from these trivial points, I'm hugely impressed by how good SANE and
xscanimage etc. are. Well done those people.

Once I've given the version of xscanimage and the net backend a thorough
testing on Digital Unix I'll send in a report and we can declare 0.73
at least partly tested and found working on DU 4.00 (I still want to try
getting the SCSI/CAM on DU working though. I'm waiting for someone to tell
me what to do.)

Ian

-----------------------------------------------------------------------------
Ian Grant, Computer Officer (HEP group), DAMTP, Silver St., Cambridge CB3 9EW

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