[sane-devel] saned -d6 OK saned fails [GishPuppy]

[m. allan noah]

see all those 'Address already in use' statements? something is
already listening on the port, perhaps inetd?

allan

On Wed, Mar 19, 2008 at 10:53 AM, Geoff Lane <bunsen at tesco.net> wrote:
> On 18 Mar 2008 at 10:27, m. allan noah wrote:
>
>  I have checked everything listed below and all looks fine.
>
>  Inetutils-inetd is shown (Via ps -Af) running as ROOT
>
>  What is puzzling me is the output of manually running saned with different values after
>  the d flag, d5 and above and it works, less than d5 and it doesn't work.
>
>  Output as follows;
>
>  xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>  geoff at challenger:~$ saned -d1
>  [saned] main: [1] bind failed: Address already in use
>
>  geoff at challenger:~$ saned -d4
>  [saned] main: starting debug mode (level 4)
>  [saned] main: [1] bind failed: Address already in use
>  [saned] main: waiting for control connection
>
>  geoff at challenger:~$ saned -d5
>  [saned] main: starting debug mode (level 5)
>  [saned] main: trying to get port for service `sane-port' (getaddrinfo)
>  [saned] main: [0] socket () using IPv6
>  [saned] main: [0] setsockopt ()
>  [saned] main: [0] bind () to port 6566
>  [saned] main: [0] listen ()
>  [saned] main: [1] socket () using IPv4
>  [saned] main: [1] setsockopt ()
>  [saned] main: [1] bind () to port 6566
>  [saned] main: [1] bind failed: Address already in use
>  [saned] main: waiting for control connection
>
>  geoff at challenger:~$
>  xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>
>  Geoff Lane
>
>  > reading the config line from right to left:
>  >
>  > listen on port 'saned', run program '/usr/sbin/saned' as user and
>  > group 'saned', and hand it the tcp stream.
>  >
>  > so, check that you have saned listed in /etc/services, the binary
>  > saned in /usr/sbin, the user saned in /etc/passwd, and the group saned
>  > in /etc/group. that should get inetd to actually listen on the port,
>  > and start the saned binary when you connect.
>  >
>  > now, the scanner device files have their own permissions, which are
>  > managed by various hotplug/udev type scripts, depending on the
>  > OS/distro. the user saned must have permission to read/write to these
>  > files as well. If your OS uses a 'scanner' group, you will probably
>  > have to add 'saned' user to that group. If your system uses some other
>  > mechanism, we will try to figure it out.
>



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