Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!usc!elroy.jpl.nasa.gov!decwrl!nsc!pyramid!infmx!kevinf
From: kevinf@infmx.UUCP (Kevin Franden)
Newsgroups: comp.unix.wizards
Subject: Re: sockets
Keywords: sockets, primer
Message-ID: <4444@infmx.UUCP>
Date: 7 Jun 90 13:34:26 GMT
References: <24943@usc.edu> <102572@convex.convex.com> <4421@infmx.UUCP>
Reply-To: kevinf@infmx.UUCP (Kevin Franden)
Organization: Informix, Menlo Park, Ca. U.S.A.
Lines: 37


Thanks to all who replied to me.  (blush, blush) Shame on me for not 
reading the man pages more carefully (blush).


Still being incredibly naieve about sockets, I attempt again:
Since last time, I have managed to get somthing flying (ok, limping =-)
I have managed to talk between an unused port (I happened to be using
6000) and I managed to steal the date/time off another machine by calling
port 13.

I've got a process listening to the port on host A and then somthing 
talking to the port on host B.  the pairs purpose is to have A send 
a string to B and have B answer back w/ a diffrent string.

I have a couple new questions now:

	1) When does /etc/services come into play?  I was able to talk
	   over port 6000 w/ no trouble (SOCK_STREAM) WITHOUT having
	   an entry in /etc/services.  Which leads me to wonder what 
	   exactly /etc/services does anyway.  Was this a cardinal sin?
	   Very dangerous?  Very stupid?  All of the above?

	2) If I understnd correctly (which I probably don't) I can 
	   use inetd to start up my executable if there's a request
	   on that port.  Will one of the true net.wizards help this
	   fledgling.wizard by explaining the functions of all these 
	   files?


-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Kevin Franden		    UUCP: {pyramid|lll-crg}!infmx!kevinf
Informix Software Inc
disclaimer("I said what I said and not my employer");
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

There are Lies, Damn lies, Statistics, Benchmarks, and Delivery dates