Received: with ECARTIS (v1.0.0; list gopher);
 Fri, 28 May 2004 14:41:07 -0500 (CDT)
Return-Path: <jgoerzen@complete.org>
X-Original-To: gopher@complete.org
Delivered-To: gopher@complete.org
Received: from localhost (localhost [127.0.0.1])
	by glockenspiel.complete.org (Postfix) with ESMTP
	id E2709F5; Fri, 28 May 2004 14:41:06 -0500 (CDT)
Received: from glockenspiel.complete.org ([127.0.0.1])
	by localhost (glockenspiel [127.0.0.1]) (amavisd-new, port 10025)
	with ESMTP id 27174-06; Fri, 28 May 2004 14:41:05 -0500 (CDT)
Received: by glockenspiel.complete.org (Postfix, from userid 1000)
	id 584732F5; Fri, 28 May 2004 14:41:05 -0500 (CDT)
Date: Fri, 28 May 2004 14:41:05 -0500
From: John Goerzen <jgoerzen@complete.org>
To: gopher@complete.org
Subject: [gopher] Re: Pygopherd and xinetd
Message-ID: <20040528194105.GB26678@complete.org>
References: <Pine.LNX.4.58.0405281105370.21687@tanatos>
 <20040528130832.GB9268@excelhustler.com>
 <Pine.LNX.4.58.0405282100380.3086@tanatos>
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.58.0405282100380.3086@tanatos>
User-Agent: Mutt/1.5.5.1+cvs20040105i
X-Virus-Scanned: by amavisd-new-20030616-p7 (Debian) at complete.org
Content-Transfer-Encoding: 8bit
X-archive-position: 926
X-ecartis-version: Ecartis v1.0.0
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
X-original-sender: jgoerzen@complete.org
Precedence: bulk
Reply-to: gopher@complete.org
List-help: <mailto:ecartis@complete.org?Subject=help>
List-unsubscribe: <mailto:gopher-request@complete.org?Subject=unsubscribe>
List-software: Ecartis version 1.0.0
List-Id: Gopher <gopher.complete.org>
X-List-ID: Gopher <gopher.complete.org>
List-subscribe: <mailto:gopher-request@complete.org?Subject=subscribe>
List-owner: <mailto:jgoerzen@complete.org>
List-post: <mailto:gopher@complete.org>
List-archive: <http://www.complete.org/mailinglists/archives/>
X-list: gopher

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.

-- John

> |> Oh, by the way, John, I noticed this typo in the pygopherd/README file:
> |
> |Oops :-)
> 
>   I want to be mentioned in the next Cahngelog!  :-D

<grin> 
> 
> 
> 
>   Sandro
> 
> 
> -- 
> Bellum se ipsum alet
>        La guerra nutre se stessa
> 
> Livio, "Ab urbe condita", XXXIV,9
> 

-- 
John Goerzen <jgoerzen@complete.org>                       www.complete.org