[sane-devel] saned -d6 OK saned fails

[m. allan noah]

the -d flag causes saned to listen on port 6566 as the user that
started it. otherwise, saned thinks it is being called from inetd, and
so expects to get handed an already connected socket.

the real question here is why does inetd not listen on 6566 for you.
this is almost certainly an inetd config issue. perhaps you do not
have the user or group on the system, or perhaps your inetd also wants
to see the line added to /etc/services?

allan

On 3/14/08, Geoff Lane <bunsen at tesco.net> wrote:
>
>  Using a network port scanner and a remote graphical scanner I cannot get either to show or
>  connect to port 6566.  If I then issue the command saned I again get no acknowledgement
>  of port 6566 but if I issue saned -d6 my graphical scanner connects from a remote computer
>  and my network port scanner shows port 6566 as available.
>
>  Any reason why this may be? I was under the impression that the -d flag was to run saned
>  in debug mode rather than assist or enable a connection.
>
>  The only reason I am experimenting with command entries is that I do have inetd installed
>  and working and have followed the  MAN  saned instructions I cannot get an
>  acknowledgement of port 6566
>
>  Geoff Lane
>  Welwyn Hatfield Computer Club
>  www.whcc.co.uk
>
>
>  --
>  sane-devel mailing list: sane-devel at lists.alioth.debian.org
>  http://lists.alioth.debian.org/mailman/listinfo/sane-devel
>  Unsubscribe: Send mail with subject "unsubscribe your_password"
>              to sane-devel-request at lists.alioth.debian.org
>


-- 
"The truth is an offense, but not a sin"