content-class: urn:content-classes:message
MIME-Version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Subject: [gopher] Please remove me from this list RE: Re: Pygopherd and xinetd
Date: Fri, 28 May 2004 15:22:26 -0400
Message-ID: <A7C2380FBDDA4D479AD587E08679CCC404717AD4@spqcexc01.exfo.com>
Thread-Topic: [gopher] Re: Pygopherd and xinetd
Thread-Index: AcRE5+glUBtUA22bSJ+9nbgTwDAkGQAAPXLg
From: "Glenna Malleau" <glenna.malleau@exfo.com>
To: <gopher@complete.org>
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
Precedence: bulk
Reply-to: gopher@complete.org

Please remove this e-mail from the list...  glenna.malleau@exfo.com
thank you

-----Original Message-----
From: Alessandro Selli [mailto:dhatarattha@route-add.net]
Sent: May 28, 2004 3:13 PM
To: gopher@complete.org
Subject: [gopher] Re: Pygopherd and xinetd


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

|From: John Goerzen <jgoerzen@complete.org>
|To: gopher@complete.org
|Date: Fri, 28 May 2004 08:08:32 -0500
|Subject: [gopher] Re: Pygopherd and xinetd
|
|On Fri, May 28, 2004 at 11:25:09AM +0200, Alessandro Selli wrote:
|>   I finally set pygopherd_2.0.9 up and running on route-add.net, =
after=20
|> installing python2.3 side to side with the server's native python2.1.
|> I noticed that I cannot run it from xinetd, when I try to I get this =
error in=20
|> the log:
|
|PyGopherd does not have any support for running from inetd or xinetd at
|present.  That support would probably be trivial to implement, but it's
|just not there right now.

  Oh well, it doesn't matter.  The old sparky has got so much RAM I can=20
leave pygopherd run all the time whithout trouble.

|Let me explain some of the errors you're getting:
|
|> May 25 20:28:16 brillante pygopherd[25192]: Pygopherd starting, using =

|> configuration file /etc/pygopherd/pygopherd.conf
|> May 25 20:28:17 brillante pygopherd[25192]: mimetypes initialized =
with files:=20
|> ['./conf/mime.types', '/etc/pygopherd/mime.types', '/etc/mime.types']
|> May 25 20:28:18 brillante pygopherd[25192]: unknown-address =
[None/None]=20
|> EXCEPTION error: (48, 'Address already in use')
|
|That's because PyGopherd attempts to listen to a port that is already
|being listened on by xinetd.

  Just as I thought!  :^)

|> May 25 20:28:18 brillante pygopherd[25192]: Application startup NOT =
successful!
|>=20
|>   When I run it as a standalone server, it runs all right.  When I =
wan to run=20
|> it as a xinetd-run service, I put "detach =3D yes" in=20

  Well, this was wrong anyway, when a server is run from xinetd it =
should not=20
detach/fork (are the two terms interchangeable?) on its own, since =
xinetd=20
takes  care of that (I realized this some time ago when I wanted Qpopper =
to=20
run from xinetd and it failed, IIRC).  I either remebered wrong what I =
did, or
I wrote the wrong thing or I messed up xinetds' configuration.

|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 =3D no" then the server is busy and does not =
answer=20
new connections until the current one ends (that is, until the current =
data=20
transfer completes)?

|> 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


  Sandro


--=20
Bellum se ipsum alet
       La guerra nutre se stessa

Livio, "Ab urbe condita", XXXIV,9