Note that this is only true if you've configured saned in /etc/inetd.conf
using TCP Wrappers (tcpd). Check the host access files if your inetd.conf
entry looks like:
sane stream tcp nowait <username> <path>/<to>/tcpd saned
instead of:
sane stream tcp nowait <username> <path>/<to>/saned saned
Unfortunately host access isn't the reason that saned bombs for me. The
logfile actually notes that the connection has been established, but when
the client queries the list of scanners everything goes kablooey (core dump
on the client).
Scott
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com