kopia lustrzana https://gitlab.com/sane-project/website
110 wiersze
4.8 KiB
HTML
110 wiersze
4.8 KiB
HTML
<!-- received="Wed Jun 2 20:52:21 1999 PDT" -->
|
|
<!-- sent="Wed, 2 Jun 1999 22:53:24 -0500" -->
|
|
<!-- name="Scott Wells" -->
|
|
<!-- email="scott@wells-inc.com" -->
|
|
<!-- subject="RE: saned: process_request: received unexpected procedure number 0" -->
|
|
<!-- id="" -->
|
|
<!-- inreplyto="" -->
|
|
<title>sane-devel: RE: saned: process_request: received unexpected procedure number 0</title>
|
|
<h1>RE: saned: process_request: received unexpected procedure number 0</h1>
|
|
<b>Scott Wells</b> (<a href="mailto:scott@wells-inc.com"><i>scott@wells-inc.com</i></a>)<br>
|
|
<i>Wed, 2 Jun 1999 22:53:24 -0500</i>
|
|
<p>
|
|
<ul>
|
|
<li> <b>Messages sorted by:</b> <a href="date.html#9">[ date ]</a><a href="index.html#9">[ thread ]</a><a href="subject.html#9">[ subject ]</a><a href="author.html#9">[ author ]</a>
|
|
<!-- next="start" -->
|
|
<li> <b>Next message:</b> <a href="0010.html">Bernd Schroeder: "Re: microtek x6 and TMA not working"</a>
|
|
<li> <b>Previous message:</b> <a href="0008.html">Danilo Godec: "Success - Primax 4800 Direct"</a>
|
|
<!-- nextthread="start" -->
|
|
<!-- reply="end" -->
|
|
</ul>
|
|
<!-- body="start" -->
|
|
Sorry so long on the response. I finally got around to screwing with this<br>
|
|
and discovered some MIGHTY interesting behavior!<br>
|
|
<p>
|
|
Okay, I configured the SANE DLL backend for both my Microtek X6 EL scanner<br>
|
|
and for net access. Net access is configured to consult localhost for<br>
|
|
scanners. I have saned being run by inetd vs. as a standalone daemon. If I<br>
|
|
run:<br>
|
|
<p>
|
|
$ scanimage -L<br>
|
|
<p>
|
|
I get:<br>
|
|
<p>
|
|
device `microtek2:/dev/sga' is a Microtek ScanMaker X6EL flatbed scanner<br>
|
|
<p>
|
|
It doesn't list the scanner through the network. I wrote a little wrapper<br>
|
|
script to initialize the environment for saned that's invoked through inetd<br>
|
|
in lieu of saned:<br>
|
|
<p>
|
|
#!/bin/sh<br>
|
|
<p>
|
|
SANE_DIR=/usr/local/SANE<br>
|
|
SANE_DEBUG_LOG=$SANE_DIR/var/log/saned.log<br>
|
|
SANE_DEBUG_DLL=128<br>
|
|
SANE_DEBUG_NET=128<br>
|
|
SANE_DEBUG_SANEI_SCSI=128<br>
|
|
SANE_DEBUG_MICROTEK2=128<br>
|
|
export SANE_DEBUG_DLL SANE_DEBUG_NET SANE_DEBUG_SANEI_SCSI<br>
|
|
SANE_DEBUG_MICROTEK2<br>
|
|
exec $SANE_DIR/sbin/saned 2> $SANE_DEBUG_LOG<br>
|
|
<p>
|
|
This way I can see everything that saned is trying to do as it goes along<br>
|
|
its merry way. Guess what?! After putting this wrapper in place everything<br>
|
|
works great!!!!<br>
|
|
<p>
|
|
Here's the output from the same scanimage device list command above after<br>
|
|
making one change to inetd to use the wrapper instead:<br>
|
|
<p>
|
|
device `microtek2:/dev/sga' is a Microtek ScanMaker X6EL flatbed scanner<br>
|
|
device `net:localhost:microtek2:/dev/sga' is a Microtek ScanMaker X6EL<br>
|
|
flatbed scanner<br>
|
|
<p>
|
|
I have to assume that there's some small bug somewhere that doesn't crop up<br>
|
|
when the debug log is written. Perhaps using the debug log works the heap<br>
|
|
or stack just enough that it doesn't blow? I don't know. It's not<br>
|
|
intermittent, either; it works consistently without a problem. For now I'll<br>
|
|
consider my problem "fixed," and hopefully others who've seen this same<br>
|
|
problem can benefit from my wrapper script above.<br>
|
|
<p>
|
|
No, this solution doesn't give me a full "warm-and-fuzzy," but it has me<br>
|
|
able to perform network scans, so I'm not complaining. Let me know if<br>
|
|
anyone figures out what the REAL solution is.<br>
|
|
<p>
|
|
Thanks for the help,<br>
|
|
Scott Wells<br>
|
|
<p>
|
|
PS: For what it's worth, I am using tcpd to fire off the saned wrapper<br>
|
|
script, but it's not a permissions problem. I've configured my host access<br>
|
|
files to allow access from machines on my LAN.<br>
|
|
<p>
|
|
<i>> This behaviour is just totally bizarre. The server is trying to respond to</i><br>
|
|
<i>> a SANE_NET_INIT request, which must only happen once, after the connection</i><br>
|
|
<i>> has already been initialised OK. I have no idea why this behaviour is</i><br>
|
|
<i>> connected with the choice to start the server from inetd. If you can find</i><br>
|
|
<i>> a way to arrange for more DEBUG levels to be on when the daemon starts</i><br>
|
|
<i>> then that would help...</i><br>
|
|
<i>></i><br>
|
|
<i>> Are you all running TCP wrappers? Not running TCP wrappers? Can people who</i><br>
|
|
<i>> have this problem say anything more about their setup? In particular I</i><br>
|
|
<i>> find it difficult to believe that this could be a Linux 2.0.3x problem,</i><br>
|
|
<i>> since I'm using 2.0.36 happily here.</i><br>
|
|
<i>></i><br>
|
|
<i>> Nick.</i><br>
|
|
<p>
|
|
<p>
|
|
<pre>
|
|
--
|
|
Source code, list archive, and docs: <a href="http://www.mostang.com/sane/">http://www.mostang.com/sane/</a>
|
|
To unsubscribe: echo unsubscribe sane-devel | mail <a href="mailto:majordomo@mostang.com">majordomo@mostang.com</a>
|
|
</pre>
|
|
<!-- body="end" -->
|
|
<p>
|
|
<ul>
|
|
<!-- next="start" -->
|
|
<li> <b>Next message:</b> <a href="0010.html">Bernd Schroeder: "Re: microtek x6 and TMA not working"</a>
|
|
<li> <b>Previous message:</b> <a href="0008.html">Danilo Godec: "Success - Primax 4800 Direct"</a>
|
|
<!-- nextthread="start" -->
|
|
<!-- reply="end" -->
|
|
</ul>
|