Hi, On Thu, Mar 07, 2002 at 06:49:02AM -0700, Brian C wrote: > Hi all. I have what I suppose is a configuration problem with saned.
Heich SANE version? There are quite some changes in 1.0.7. > I have a system called enterprise that has a mustek:/dev/scanner attached. > If I issue the command "scanimage -T mustek:/dev/scanner" it works fine. > Also, if I issue the command "scanimage -T net:localhost:mustek:/dev/scanner" > it works fine. Even just "scanimage -T localhost" works. Even "scanimage -T the_sky_is_blue" will work :-) This doesn't mean anything. Ok, it means that your scanner is working locally. If you want to test if scanning with saned works, add localhost to enterprise's net.conf and try "scanimage -d net:localhost:mustek:/dev/scanner". Or just do "scanimage -L". This should also list yout network scanner. E.g.: hmg@hmg1:~$ scanimage -L device mustek:/dev/scanner' is a Mustek 600S/600 II CD flatbed scanner device mustek:/dev/sg0' is a Mustek 600S/600 II CD flatbed scanner If this doesn't work, your problem is on "enterprise". You can debug the client side with something like SANE_DEBUG_NET=255 scanimage -L The server side (saned) is a bit trickier. Remove/comment out the entry for saned in (x)inetd.conf, sigHUP inetd and start saned maually with debugging enabled: "saned -d255". Depending on the version of SANE you will find debug messages in syslog or stderr. You can additionally use the normal DBG output for the mustek backend if you think it's a problem with this backend: "SANE_DEBUG_MUSTEK=255 saned -d255". Now start (at another console) scanimage -L. You must restart saned manually after each connection in this debug mode. > The problem lies when I try to access it from another workstation called > defiant. Tough little ship :-) > No matter which variation of the above network commands I give > (using enterprise instead of localhost) I get this error: "scanimage: no SANE > devices found." > Do I NEED a 'hosts.equiv' file or can I skip that? It seems to make no > difference. Ignore this file. Maybe we should remove support completely. > -- /var/log/daemons/info ------------------------------------------- > Mar 7 06:26:49 Enterprise saned[3523]: access by saned-user@Defiant accepted > Mar 7 06:26:51 Enterprise saned[3523]: exiting Access was accepted so the problem seems to occur later. There have been some problems with saned in older versions leeding to segfaults or other exits. So if you have a version before 1.0.7 this may be a reason. > -- hosts.allow on enterprise ----------------------------------------- > # > # hosts.allow This file describes the names of the hosts which are > # allowed to use the local INET services, as decided > # by the '/usr/sbin/tcpd' server. > # > # > > defiant > voyager > runabout > localhost > enterprise > --------------------------------------------------------------------------- Isn't the format of this file something like "dameon : client"? But as saned accepted your access, it shouldn't matter in your case. Bye, Henning
