Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!gatech!hao!woods
From: woods@hao.UCAR.EDU (Greg Woods)
Newsgroups: comp.protocols.tcp-ip
Subject: socket states
Message-ID: <739@hao.UCAR.EDU>
Date: Thu, 18-Jun-87 03:36:17 EDT
Article-I.D.: hao.739
Posted: Thu Jun 18 03:36:17 1987
Date-Received: Sun, 21-Jun-87 11:49:30 EDT
Organization: High Altitude Obs./NCAR, Boulder CO
Lines: 15

For us beginners with TCP and sockets, and after reading the recent discussion
here about LAST_ACK and FIN_WAIT_2 states, I would be very interested (and
I suspect I'm not the only one) in reading an explanation of what the various
socket states are and exactly what they mean. I'm the site admin for a machine
that is very new on the Internet, and due to the cost difference, I've had
to shift from phone line uucp links to NNTP/SMTP internet links as much as
I can, which now accounts for 80+% of our traffic, but I still don't understand
how this stuff really works, nor is there any good information from a system
administrator's point of view on it (I'm NOT a kernel hacker).

--Greg
-- 
UUCP: {hplabs, seismo, nbires, noao}!hao!woods
CSNET: woods@ncar.csnet  ARPA: woods%ncar@CSNET-RELAY.ARPA
INTERNET: woods@hao.ucar.edu