sane-project-website/old-archive/2001-06/0068.html

148 wiersze
6.7 KiB
HTML

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"
"http://www.w3.org/TR/REC-html40/loose.dtd">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=UTF-8">
<TITLE>sane-devel: Re: xsane requests username and password after sane</TITLE>
<META NAME="Author" CONTENT="Nick Lamb (njl98r@ecs.soton.ac.uk)">
<META NAME="Subject" CONTENT="Re: xsane requests username and password after saned has exited">
</HEAD>
<BODY BGCOLOR="#FFFFFF" TEXT="#000000">
<H1>Re: xsane requests username and password after saned has exited</H1>
<!-- received="Mon Jun 4 11:42:33 2001" -->
<!-- isoreceived="20010604184233" -->
<!-- sent="Mon, 4 Jun 2001 19:44:22 +0100" -->
<!-- isosent="20010604184422" -->
<!-- name="Nick Lamb" -->
<!-- email="njl98r@ecs.soton.ac.uk" -->
<!-- subject="Re: xsane requests username and password after saned has exited" -->
<!-- id="20010604194422.A25439@ecs.soton.ac.uk" -->
<!-- charset="UTF-8" -->
<!-- inreplyto="3B1B843E.80B4C930@rauch-domain.de" -->
<STRONG>From:</STRONG> Nick Lamb (<A HREF="mailto:njl98r@ecs.soton.ac.uk?Subject=Re:%20xsane%20requests%20username%20and%20password%20after%20saned%20has%20exited&In-Reply-To=&lt;20010604194422.A25439@ecs.soton.ac.uk&gt;"><EM>njl98r@ecs.soton.ac.uk</EM></A>)<BR>
<STRONG>Date:</STRONG> Mon Jun 04 2001 - 11:44:22 PDT
<P>
<!-- next="start" -->
<LI><STRONG>Next message:</STRONG> <A HREF="0069.html">Henning Meier-Geinitz: "Semaphores (sys/sem.h) in sane-backends"</A>
<UL>
<LI><STRONG>Previous message:</STRONG> <A HREF="0067.html">Franz Bakan: "Re: Compiling on OS/2"</A>
<LI><STRONG>In reply to:</STRONG> <A HREF="0058.html">Oliver Rauch: "Re: xsane requests username and password after saned has exited"</A>
<!-- nextthread="start" -->
<LI><STRONG>Next in thread:</STRONG> <A HREF="0070.html">Chris Pinkham: "Re: xsane requests username and password after saned has exited"</A>
<LI><STRONG>Next in thread:</STRONG> <A HREF="0060.html">Oliver Rauch: "Re: xsane requests username and password after saned has exited"</A>
<LI><STRONG>Reply:</STRONG> <A HREF="0070.html">Chris Pinkham: "Re: xsane requests username and password after saned has exited"</A>
<LI><STRONG>Reply:</STRONG> <A HREF="0072.html">Henning Meier-Geinitz: "Re: xsane requests username and password after saned has exited"</A>
<LI><STRONG>Reply:</STRONG> <A HREF="0093.html">Oliver Rauch: "Re: xsane requests username and password after saned has exited"</A>
<!-- reply="end" -->
<LI><STRONG>Messages sorted by:</STRONG>
<A HREF="date.html#68">[ date ]</A>
<A HREF="index.html#68">[ thread ]</A>
<A HREF="subject.html#68">[ subject ]</A>
<A HREF="author.html#68">[ author ]</A>
</UL>
<HR NOSHADE><P>
<!-- body="start" -->
<P>
On Mon, Jun 04, 2001 at 02:51:10PM +0200, Oliver Rauch wrote:
<BR>
<EM>&gt; Hi Nick,
</EM><BR>
<EM>&gt;
</EM><BR>
<EM>&gt; I think the reason is if the frontend dies and does not inform saned to exit
</EM><BR>
<EM>&gt; then saned never will exit at all.
</EM><BR>
<P>Without trying it my understanding is that on anything vaguely modern
<BR>
(are people trying to use SANE from DOS? from Windows 3.1?) the TCP stack
<BR>
is an OS component and will perform a full TCP shutdown on behalf of the
<BR>
frontend. So this can ONLY happen when a user turns off their PC while
<BR>
using the frontend -- little wonder that things break if you do that!
<BR>
<P>Does anyone have evidence to contradict that? Once again I ask for the
<BR>
person who added this watchdog timer kludge to step forward.
<BR>
<P><EM>&gt; The fork() in sane-net has the advantage that the network protocol works
</EM><BR>
<EM>&gt; invisiblie for the fronten, no frontend has to care about.
</EM><BR>
<EM>&gt;
</EM><BR>
<EM>&gt; The advantage of the frontend initiated keep alive package is that we
</EM><BR>
<EM>&gt; don<6F>t need to create a separate keep-alive process.
</EM><BR>
<EM>&gt;
</EM><BR>
<EM>&gt; May be we could define a well_known_option &quot;create_keepalives&quot; that can be
</EM><BR>
<EM>&gt; set by GUI-frontends, so for command-line-frontends the fork() is not called.
</EM><BR>
<P>I think this problem (user turns off PC while using scanner remotely)
<BR>
is rare enough not to require extreme measures. Try this instead, one
<BR>
step at a time
<BR>
<P>0. Eliminate the watchdog timer
<BR>
&nbsp;&nbsp;&nbsp;This will make SANE behave properly for the _normal_ case
<BR>
<P>1. Turn on TCP keep alive socket option in saned where available
<BR>
&nbsp;&nbsp;&nbsp;This makes it recover (eventually) from PC crash
<BR>
<P>2. Permit null operation/ null result packets from the server
<BR>
&nbsp;&nbsp;&nbsp;and send these to elicit ACK vs RST indicator from client TCP stack
<BR>
<P>Note that the first two require NO CHANGE to the remote client, and
<BR>
the last one if it turns out to be necessary requires only some
<BR>
small changes, maybe a dozen lines.
<BR>
<P>Nick.
<BR>
<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?Subject=Re:%20xsane%20requests%20username%20and%20password%20after%20saned%20has%20exited&In-Reply-To=&lt;20010604194422.A25439@ecs.soton.ac.uk&gt;">majordomo@mostang.com</A>
</PRE>
<P><!-- body="end" -->
<HR NOSHADE>
<UL>
<!-- next="start" -->
<LI><STRONG>Next message:</STRONG> <A HREF="0069.html">Henning Meier-Geinitz: "Semaphores (sys/sem.h) in sane-backends"</A>
<LI><STRONG>Previous message:</STRONG> <A HREF="0067.html">Franz Bakan: "Re: Compiling on OS/2"</A>
<LI><STRONG>In reply to:</STRONG> <A HREF="0058.html">Oliver Rauch: "Re: xsane requests username and password after saned has exited"</A>
<!-- nextthread="start" -->
<LI><STRONG>Next in thread:</STRONG> <A HREF="0070.html">Chris Pinkham: "Re: xsane requests username and password after saned has exited"</A>
<LI><STRONG>Next in thread:</STRONG> <A HREF="0060.html">Oliver Rauch: "Re: xsane requests username and password after saned has exited"</A>
<LI><STRONG>Reply:</STRONG> <A HREF="0070.html">Chris Pinkham: "Re: xsane requests username and password after saned has exited"</A>
<LI><STRONG>Reply:</STRONG> <A HREF="0072.html">Henning Meier-Geinitz: "Re: xsane requests username and password after saned has exited"</A>
<LI><STRONG>Reply:</STRONG> <A HREF="0093.html">Oliver Rauch: "Re: xsane requests username and password after saned has exited"</A>
<!-- reply="end" -->
<LI><STRONG>Messages sorted by:</STRONG>
<A HREF="date.html#68">[ date ]</A>
<A HREF="index.html#68">[ thread ]</A>
<A HREF="subject.html#68">[ subject ]</A>
<A HREF="author.html#68">[ author ]</A>
</UL>
<!-- trailer="footer" -->
<HR NOSHADE>
<P>
<SMALL>
<EM>
This archive was generated by <A HREF="http://www.hypermail.org/">hypermail 2b29</A>
: <EM>Mon Jun 04 2001 - 11:43:56 PDT</EM>
</EM>
</SMALL>
</BODY>
</HTML>