kopia lustrzana https://gitlab.com/sane-project/website
140 wiersze
6.2 KiB
HTML
140 wiersze
6.2 KiB
HTML
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"
|
||
"http://www.w3.org/TR/REC-html40/loose.dtd">
|
||
<HTML>
|
||
<HEAD>
|
||
<TITLE>sane-devel: Re: xsane requests username and password after sane</TITLE>
|
||
<META NAME="Author" CONTENT="Henning Meier-Geinitz (henning@meier-geinitz.de)">
|
||
<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 09:59:29 2001" -->
|
||
<!-- isoreceived="20010604165929" -->
|
||
<!-- sent="Mon, 4 Jun 2001 18:56:32 +0200" -->
|
||
<!-- isosent="20010604165632" -->
|
||
<!-- name="Henning Meier-Geinitz" -->
|
||
<!-- email="henning@meier-geinitz.de" -->
|
||
<!-- subject="Re: xsane requests username and password after saned has exited" -->
|
||
<!-- id="20010604185632.A14406@vortex.swb.de" -->
|
||
<!-- inreplyto="3B1B843E.80B4C930@rauch-domain.de" -->
|
||
<STRONG>From:</STRONG> Henning Meier-Geinitz (<A HREF="mailto:henning@meier-geinitz.de?Subject=Re:%20xsane%20requests%20username%20and%20password%20after%20saned%20has%20exited&In-Reply-To=<20010604185632.A14406@vortex.swb.de>"><EM>henning@meier-geinitz.de</EM></A>)<BR>
|
||
<STRONG>Date:</STRONG> Mon Jun 04 2001 - 09:56:32 PDT
|
||
<P>
|
||
<!-- next="start" -->
|
||
<LI><STRONG>Next message:</STRONG> <A HREF="0066.html">SCC: "Re: umax 2200 hi res scan"</A>
|
||
<UL>
|
||
<LI><STRONG>Previous message:</STRONG> <A HREF="0064.html">lee: "Re: UMAX Vistascan S12"</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="0085.html">Oliver Rauch: "Re: xsane requests username and password after saned has exited"</A>
|
||
<LI><STRONG>Next in thread:</STRONG> <A HREF="0068.html">Nick Lamb: "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="0085.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#65">[ date ]</A>
|
||
<A HREF="index.html#65">[ thread ]</A>
|
||
<A HREF="subject.html#65">[ subject ]</A>
|
||
<A HREF="author.html#65">[ author ]</A>
|
||
</UL>
|
||
<HR NOSHADE><P>
|
||
<!-- body="start" -->
|
||
<P>
|
||
Hi,
|
||
<BR>
|
||
<P>On Mon, Jun 04, 2001 at 02:51:10PM +0200, Oliver Rauch wrote:
|
||
<BR>
|
||
<EM>> I think the reason is if the frontend dies and does not inform saned to exit
|
||
</EM><BR>
|
||
<EM>> then saned never will exit at all.
|
||
</EM><BR>
|
||
<P>At least on Linux, saned will exit even if you kill -9 xsane. I don't
|
||
<BR>
|
||
understand all details but maybe that's because of signal (SIGPIPE, quit)
|
||
<BR>
|
||
in saned.c. So maybe this is for other platforms?
|
||
<BR>
|
||
<P><EM>> we have to decide what we have to do.
|
||
</EM><BR>
|
||
<EM>> When saned never exits when the frontend dies without calling sane_exit or sane_close
|
||
</EM><BR>
|
||
<EM>> then we need the watchdog. In this case I see two possibilities:
|
||
</EM><BR>
|
||
<EM>> 1) sane-net does fork() and starts a process that sends a keep-alive package e.g. ever 60 seconds.
|
||
</EM><BR>
|
||
<EM>> 2) the frontend has to initiate the keep alive package.
|
||
</EM><BR>
|
||
<EM>>
|
||
</EM><BR>
|
||
<EM>> A keep alive packge e.g. could be to read the option numbers (option number 0).
|
||
</EM><BR>
|
||
<EM>>
|
||
</EM><BR>
|
||
<EM>> The fork() in sane-net has the advantage that the network protocol works
|
||
</EM><BR>
|
||
<EM>> invisiblie for the fronten, no frontend has to care about.
|
||
</EM><BR>
|
||
<EM>>
|
||
</EM><BR>
|
||
<EM>> The advantage of the frontend initiated keep alive package is that we
|
||
</EM><BR>
|
||
<EM>> don<6F>t need to create a separate keep-alive process.
|
||
</EM><BR>
|
||
<P>I haven't looked into details but don't we need some sort of locking for
|
||
<BR>
|
||
this? What happens, if some data is transmitted through the net and in
|
||
<BR>
|
||
this moment the forked process starts its sane_get_option_descriptor (handle, 0)
|
||
<BR>
|
||
function?
|
||
<BR>
|
||
<P><EM>> May be we could define a well_known_option "create_keepalives" that can be
|
||
</EM><BR>
|
||
<EM>> set by GUI-frontends, so for command-line-frontends the fork() is not called.
|
||
</EM><BR>
|
||
<P>I'm not sure if this is necessary as the keep-alive shouldn't harm
|
||
<BR>
|
||
command-line frontends (it's just not necessary).
|
||
<BR>
|
||
<P>I will change the alarm to 3600 seconds for now.
|
||
<BR>
|
||
<P>Bye,
|
||
<BR>
|
||
Henning
|
||
<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=<20010604185632.A14406@vortex.swb.de>">majordomo@mostang.com</A>
|
||
</PRE>
|
||
<P><!-- body="end" -->
|
||
<HR NOSHADE>
|
||
<UL>
|
||
<!-- next="start" -->
|
||
<LI><STRONG>Next message:</STRONG> <A HREF="0066.html">SCC: "Re: umax 2200 hi res scan"</A>
|
||
<LI><STRONG>Previous message:</STRONG> <A HREF="0064.html">lee: "Re: UMAX Vistascan S12"</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="0085.html">Oliver Rauch: "Re: xsane requests username and password after saned has exited"</A>
|
||
<LI><STRONG>Next in thread:</STRONG> <A HREF="0068.html">Nick Lamb: "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="0085.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#65">[ date ]</A>
|
||
<A HREF="index.html#65">[ thread ]</A>
|
||
<A HREF="subject.html#65">[ subject ]</A>
|
||
<A HREF="author.html#65">[ 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 - 09:59:57 PDT</EM>
|
||
</EM>
|
||
</SMALL>
|
||
</BODY>
|
||
</HTML>
|