[gopher] Re: Pygopherd and xinetd

[John Goerzen <jgoerzen@xxxxxxxxxxxx>]

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@xxxxxxxxxxxx>                       www.complete.org