Path: utzoo!utgpu!cunews!bnrgate!brtph3!brchh104!brchs1!bnr.ca!rice!sun-spots-request
From: kory@avatar.avatar.com (Kory Hamzeh)
Newsgroups: comp.sys.sun
Subject: Timewait on TCP connections
Keywords: Networks
Message-ID: <258@brchh104.bnr.ca>
Date: 16 Nov 90 12:05:00 GMT
Sender: news@brchh104.bnr.ca
Organization: Sun-Spots
Lines: 17
Approved: Sun-Spots@rice.edu
X-Original-Date: Tue Oct 30 19:49:11 1990
X-Sun-Spots-Digest: Volume 9, Issue 363, message 10
X-Note: Submissions: sun-spots@rice.edu, Admin: sun-spots-request@rice.edu

Is there anyway to get a TCP connect to NOT go into TIMEWAIT mode after
the connection is closed on that port. We have several demons which
re-start very quickly after termination, however, ussually they can't bind
their addresses because that port is in TIMEWAIT mode.

I didn't see any socket or connect option in the man pages that could
explain this. And just for the hell of it, I explicitly disabled the
SO_LINGER socket option. Didn't help.

I am running SunOS 4.1.

Any help would be greatly appreciated.

Thanks.

Kory Hamzeh             UUCP: avatar!kory or ..!uunet!avatar!kory
                    INTERNET: kory@avatar.com