Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uunet!mcsun!ukc!edcastle!elev26
From: elev26@castle.ed.ac.uk (Gerard A. Allan)
Newsgroups: comp.unix.wizards
Subject: Re: sockets
Keywords: sockets, primer
Message-ID: <4529@castle.ed.ac.uk>
Date: 6 Jun 90 12:25:30 GMT
References: <24943@usc.edu> <102572@convex.convex.com> <4421@infmx.UUCP>
Reply-To: elev26@castle.ed.ac.uk (Gerard A. Allan)
Organization: Edinburgh Microfabrication Facility
Lines: 37

In article <4421@infmx.UUCP> kevinf@infmx.UUCP (Kevin Franden) writes:
>
>Being incredibly naieve about sockets, I ask this blindly:
>
>Doesn't there exist a function to determin a preexisiting (I've 
>heard some call this a "wellknown") service's socket number?

sounds like you want, 
                    struct servent *getservbyname(name, proto)
                    char *name, *proto;

There seems to have been a lot of questions on sockets recently (I don't
want to discourage them since I learn a lot from the answers), there are a
couple of good sources of information that will answer most users questions

1)   ``An Introductory 4.3BSD Interprocess Communication
     Tutorial.'' (reprinted in UNIX Programmer's Supplementary
     Documents Volume 1, PS1:7)

This give a *very* clear introduction to sockets (University Libs should
have a copy)

Follow up by reading,

2)   ``An Advanced 4.3BSD Interprocess
     Communication Tutorial.'' (reprinted in UNIX Programmer's
     Supplementary Documents Volume 1, PS1:8)

Once you've read these you could probably answer most of the socket
related questions ask here recently.

Gerard A. Allan                                 | Post:  EMF
elev26@castle.ed.ac.uk                          |        Kings Buildings
JANET:elev26@uk.ac.ed.castle                    |        University of Edinburgh
Internet:elev26%castle.ed.ac.uk@cunyvm.cuny.edu |        Edinburgh
EARN/BITNET:elev26%castle.ed.ac.uk@UKACRL       |        Scotland
UUCP:elev26%castle.ed.ac.uk@ukc.uucp            |        EH9 3JL