Path: utzoo!utgpu!watmath!att!tut.cis.ohio-state.edu!cs.utexas.edu!usc!rutgers!elbereth.rutgers.edu!ron.rutgers.edu!ron
From: ron@ron.rutgers.edu (Ron Natalie)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: novice TCP-IP / UNIX questions
Message-ID: 
Date: 15 Aug 89 20:34:57 GMT
References: <1149@sas.UUCP>
Distribution: comp.protocols.tcp-ip
Organization: Rutgers Univ., New Brunswick, N.J.
Lines: 31

Question 1:  do i accept connections on descriptor 0, 
       -or-  do i read/write it hoping that inetd accepted
            the connection for me?
       -or   am i supposed to bind it in some fashion?

Answer 1:  Number 2 is correct.  Inetd accepts the connection for you and
	forces it to be file descriptor zero.

Question 2:  any tips on how to debug a process launched by inetd?

Answer 2:  Most of the inetd started servers have a -d option that allows
	you to start up the job with the old socket/bind/accept sequence
	so you can test it without having to change the inetd configuration.
	Actually, since all that grungy bind stuff is taken care of it's
	easier to write inetd applications.

Question 3:  i ultimately want to write client/server code to support
             communications between two SAS sessions via the internet.
             (SAS/Share and micro-to-host link if you know our products)
             how do i request that a well know number be assigned to
             my/SAS's application?

Answer 3:  The numbers are enumerated in a document known as assigned
	numbers.  My guess is that Postel is still responsible for
	dealing them out.


> paul kent, SAS Institute, box 8000, cary nc 27512-8000 -- 919 467 8000

Gee, that address sounds familiar.  Seems to be on a few zillion output runs
here.