[gopher] Re: Pygopherd and xinetd

[Alessandro Selli <dhatarattha@xxxxxxxxxxxxx>]

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