# Re: net problem

Andreas Beck (becka@rz.uni-duesseldorf.de)
Sun, 22 Aug 1999 14:52:07 +0200

- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
- Next message: Oliver Rauch: "xsane-0.33 available"
- Previous message: Oliver Rauch: "sane-umax-build-9"

> Added
> sane 6566/tcp # network scanner daemon
> to /etc/services
Correct.

> sane stream tcp nowait root /usr/local/sbin/saned saned
> to /etc/inetd.conf

The root is not so nice, but o.k. for testing. I myself use "nobody" and
have a setgid saned for minimum risk, but for a first test, root should be
o.k.

And I suppose you have sent SIGHUP to inetd, so it rereads its config -
right ?

> localhost
> to /usr/local/etc/sane.d/net.conf
Right.

> uncommented net in dll.conf
Yep.

> this is the output I get (with SANE_DEBUG_NET=128), the first
> succesfull probe is from the local microtek2 backend, the other
> failing probe is from the net driver. Needless to say, the net

> [sanei_init_debug]: Setting debug level of net to 128.
> [net] adding backend localhost
> [net] get_devices: ignoring rpc-returned status Unknown SANE status code 168448867

This is very weird. This sounds like the sane daemon failing very very early
or not connecting at all. Try straceing both sides of the connection.
The logs should give a clue on that.

The daemon side might be a bit tricky, as it appears, when the connection is
made, started from inetd. There are two possible ways to get around this:

1. Make a small script "ssaned", that looks like
#!/bin/bash
exec strace saned 2>/tmp/logfile

2. use "strace -p [pid_of_inetd] -f" to attach to the inetd, and "-f"ollow
when it forks off the saned.

CU, Andy

    --
    = Andreas Beck                    |  Email :  <andreas.beck@ggi-project.org> =

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

     Next message: Oliver Rauch: "xsane-0.33 available"
     Previous message: Oliver Rauch: "sane-umax-build-9"