Date: Fri, 28 May 2004 22:50:13 +0200 (CEST)
From: Alessandro Selli <dhatarattha@route-add.net>
To: gopher@complete.org
Subject: [gopher] Re: Pygopherd and xinetd
In-Reply-To: <20040528194105.GB26678@complete.org>
Message-ID: <Pine.LNX.4.58.0405282246180.3086@tanatos>
References: <Pine.LNX.4.58.0405281105370.21687@tanatos>
 <20040528130832.GB9268@excelhustler.com>
 <Pine.LNX.4.58.0405282100380.3086@tanatos>
 <20040528194105.GB26678@complete.org>
MIME-Version: 1.0
Content-type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
Precedence: bulk
Reply-to: gopher@complete.org

Il giorno Fri, 28 May 2004, John Goerzen cosė ha scritto:

|On Fri, May 28, 2004 at 09:12:58PM +0200, Alessandro Selli wrote:
|> |Unfortunately, all detach does is tell PyGopherd to run as a Unix daemon
|> |-- that is, it forks itself off, continues listening for connections in
|> |the backgrouns, and returns immediately.
|> 
|>   So, if I put "detach = no" then the server is busy and does not answer 
|> new connections until the current one ends (that is, until the current data 
|> transfer completes)?
|
|No, the server still runs exactly the same when you set detach = no, but
|you don't get your shell prompt back.  You can Ctrl-C to terminate the
|thing.

  All right, so the server *forks* every time it receives a connection 
request, indipendently from the fact that it *detaches* from the control 
terminal or not, right?


  Sandro


-- 
Bellum se ipsum alet
       La guerra nutre se stessa

Livio, "Ab urbe condita", XXXIV,9