Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!noose.ecn.purdue.edu!en.ecn.purdue.edu!longshot
From: longshot@en.ecn.purdue.edu (Without Reason)
Newsgroups: comp.unix.programmer
Subject: Re: More questions on sockets
Message-ID: <1991Jun19.124326.11811@en.ecn.purdue.edu>
Date: 19 Jun 91 12:43:26 GMT
References: <1991Jun18.050654.17373@thunder.mcrcim.mcgill.edu> <CHRIS.91Jun18100547@asylum.gsfc.nasa.gov> <14446@dog.ee.lbl.gov>
Organization: Purdue University Engineering Computer Network
Lines: 21

>In article <CHRIS.91Jun18100547@asylum.gsfc.nasa.gov>
>chris@asylum.gsfc.nasa.gov (Chris Shenton) writes:
>>I've encountered the same thing, and came up with the same non-fix. Any
>>idea how long you have to wait (don't say ``until the port's free'' :-).
>>Why?
>
>Well, actually, it really *is* `until the port is free'.
>
>There are two things going on:
    [deleted stuff about a &b]

	I have also run into this problem and wondered if shutdown(2)
  would do the trick.  I plan to try this with a server I have, but wondered
  if anyone else has tried it?

--longshot
-- 
longshot@ecn.purdue.edu	   (Rich Long)

  To be "remembered with an affection and veneration that shall surge high
     above the waters of oblivion and glisten through the rust of time."