erlug
[Top] [All Lists]

[Erlug] saned+xinetd (lunghetta)

To: Erlug <erlug@xxxxxxxxxxxxxx>
Subject: [Erlug] saned+xinetd (lunghetta)
From: xpicio <xpicio@xxxxxxxxx>
Date: 04 Feb 2003 18:06:27 +0100
Salve a tutti.
Sto cercando invano di configurare sane in modo che sia possibile usare
lo scanner senza essere root. Lo scanner è un Mustek 600SEP, che
funziona alla perfezione con sane ma solo con root.
La via che sto cercando di percorrere è quella di far partire sane
tramite xinetd, quindi come da pagina man ho creato il file
/etc/xinetd.d/sane :

service sane
{
        disable     = no
        port        = 6566
        socket_type = stream
        wait        = no
        user        = saned
        group       = saned
        server      = /usr/sbin/saned
        server_args = -s128
}

e messo in /etc/services la riga :

sane            6566/tcp        #SANE network scanner daemon

Riavvio xinetd e sembra tutto ok :

Feb  4 17:32:00 spidey xinetd[1441]: xinetd Version 2.3.7 started with
libwrap options compiled in.
Feb  4 17:32:00 spidey xinetd[1441]: Started working: 2 available
services
Feb  4 17:32:01 spidey xinetd: Avvio xinetd succeeded

I due servizi di xinetd sono sane e tftp (che tra parentesi anche questo
non va....), e quando vado a lanciare :

[xpicio@spidey xpicio]$scanimage -d net:spidey:mustek_pp -h

non ottengo nessun dispositivo e xinetd mi risponde così :

Feb  4 17:34:55 spidey xinetd[1441]: START: sane pid=1447
from=192.168.1.2
Feb  4 17:34:55 spidey saned[1447]: main: starting debug mode (level
128)
Feb  4 17:34:55 spidey saned[1447]: main: trying to get port for service
`sane'
(getservbyname)
Feb  4 17:34:55 spidey saned[1447]: main: port is 6566
Feb  4 17:34:55 spidey saned[1447]: main: socket ()
Feb  4 17:34:55 spidey saned[1447]: main: setsockopt ()
Feb  4 17:34:55 spidey saned[1447]: main: bind ()
Feb  4 17:34:55 spidey saned[1447]: main: bind failed: Address already
in use
Feb  4 17:34:55 spidey xinetd[1441]: START: sane pid=1448
from=192.168.1.2
Feb  4 17:34:56 spidey saned[1448]: main: starting debug mode (level
128)
Feb  4 17:34:56 spidey saned[1448]: main: trying to get port for service
`sane'
(getservbyname)
Feb  4 17:34:56 spidey saned[1448]: main: port is 6566
Feb  4 17:34:56 spidey saned[1448]: main: socket ()
Feb  4 17:34:56 spidey saned[1448]: main: setsockopt ()
Feb  4 17:34:56 spidey saned[1448]: main: bind ()
Feb  4 17:34:56 spidey saned[1448]: main: bind failed: Address already
in use

La mia domanda è chi sta usando la 6566??? Non è che si pestano i piedi
saned e xinetd (la sparo)???

Come se non bastasse la cosa strana è che se uccido xinetd e lancio
saned con i parametri per il debug -s128 o -d128, e lancio scanimage
come sopra funziona, ma al termine di scanimage o xsane che sia il
demone saned si autouccide ecco l'ennesimo log :

[saned] main: starting debug mode (level 128)
[saned] main: trying to get port for service `sane' (getservbyname)
[saned] main: port is 6566
[saned] main: socket ()
[saned] main: setsockopt ()
[saned] main: bind ()
[saned] main: listen ()
[saned] main: waiting for control connection
[saned] check_host: access by remote host: 192.168.1.2
[saned] check_host: remote host is not IN_LOOPBACK
[saned] check_host: local hostname: spidey
[saned] check_host: local hostname (from DNS): spidey.comics.it
[saned] check_host: local host address (from DNS): 192.168.1.2
[saned] check_host: remote host has same addr as local: access accepted
[saned] init: access by saned-user@xxxxxxxxxxx accepted
[saned] process_request: waiting for request
[saned] process_request: got request 2
[saned] process_request: access to resource `mustek_pp' accepted
[saned] process_request: waiting for request
[saned] process_request: got request 4
[saned] process_request: waiting for request
[saned] process_request: got request 5
[saned] process_request: waiting for request
[saned] process_request: got request 5
[saned] process_request: waiting for request
[saned] process_request: got request 5
[saned] process_request: waiting for request
[saned] process_request: got request 5
[saned] process_request: waiting for request
[saned] process_request: got request 5
[saned] process_request: waiting for request
[saned] process_request: got request 5
[saned] process_request: waiting for request
[saned] process_request: got request 5
[saned] process_request: waiting for request
[saned] process_request: got request 5
[saned] process_request: waiting for request
[saned] process_request: got request 5
[saned] process_request: waiting for request
[saned] process_request: got request 5
[saned] process_request: waiting for request
[saned] process_request: got request 5
[saned] process_request: waiting for request
[saned] process_request: got request 5
[saned] process_request: waiting for request
[saned] process_request: got request 5
[saned] process_request: waiting for request
[saned] process_request: got request 5
[saned] process_request: waiting for request
[saned] process_request: got request 5
[saned] process_request: waiting for request
[saned] process_request: got request 5
[saned] process_request: waiting for request
[saned] process_request: got request 5
[saned] process_request: waiting for request
[saned] process_request: got request 5
[saned] process_request: waiting for request
[saned] process_request: got request 5
[saned] process_request: waiting for request
[saned] process_request: got request 1
[saned] process_request: waiting for request
[saned] process_request: got request 3
[saned] process_request: waiting for request
[saned] process_request: got request 10
[saned] quit: exiting

Altra cosa. Se invece lancio saned senza le opzioni per il debug il
lancio di scanimage dà esito negativo. Quindi????

Dimenticavo che il sane a mia disposizione è la versione 1.0.8 con
RedHat8.0.

Ci sono dei suggerimenti???

Bye Bye

Attachment: signature.asc
Description: Questa parte del messaggio =?ISO-8859-1?Q?=E8?= firmata

<Prev in Thread] Current Thread [Next in Thread>
  • [Erlug] saned+xinetd (lunghetta), xpicio <=