> <console> 0600 <scanner> 0600 root
> <console> 0600 <scanner> 0660 root.scanner
Scanners can be a real pain to deal with, especially when using saned to
connect from remote hosts.
I have my scanner/printer attached to my linux desktop. From there I
have saned set up so that I scan from the linux computer itself, or from
mine or my wifes laptop using the xsane mac/windows ports.
The only place the scanner will work correctly, by default, is the
desktop itself.
I went ahead and created a user 'saned' to login the saned daemon using
the nologin shell, and configured saned.conf to allow the desired hosts
to connect, and then xinetd to listen for saned requests.
I had to basically do the same as listed above except mine ended up
being root.saned. When the console.perms runs it changes the owner from
root to whoever is logged in, but fortunately leaves the group as saned.
This allows sane to work from any of the computers I want. Mild headache
to set up the first time, but now it just works.
There may be a simpler way, but that was the best I was able to figure
out... definitely not intuitive, but doable.
