From: yug on
Hi,

Given a socket descriptor, is there a way to detect what state
(CLOSE_WAIT, LAST_ACK, TIME_WAIT...) the given socket is in without
doing a write or read on the socket?

Thanks for your response,
Yug

From: Nils O. SelÄsdal on
yug(a)hotmail.com wrote:
> Hi,
>
> Given a socket descriptor, is there a way to detect what state
> (CLOSE_WAIT, LAST_ACK, TIME_WAIT...) the given socket is in without
> doing a write or read on the socket?
There seems to be no standard way. Linux has the TCP_INFO getsockopt
that seems to provide such info. It appears to not be well documented.
From: Rick Jones on
yug(a)hotmail.com wrote:
> Given a socket descriptor, is there a way to detect what state
> (CLOSE_WAIT, LAST_ACK, TIME_WAIT...) the given socket is in without
> doing a write or read on the socket?

You seem to have asked this question in at least two separate
newsgroups. As such, you may find the following helpful:

One can specify more than one newsgroup in the Newsgroups: line. The
format would look like this:

Newsgroups: group1,group2,group3

with no spaces in the grouplist. This has several advantages (so long
as it is not abused by posting messages to inappropriate groups). Only
one copy of your message must traverse the Internet, saving network
bandwidth; only one copy of your message must be stored on each news
server on the Internet, saving many MB of space world-wide; you only
have to enter the news posting once, saving you time; people only have
to read/skip your post once, saving them time; all responses in any
group can be seen in all groups, keeping everyone up to date with the
conversation.

Also, you can add a Followup-to: header line which will direct all the
follow-ups to a particular group, making it easier for you to look for
responses.

I hope you find this helpful. If you do, please pass it along to your
peers as you see them needing the same advice.

sincerely,

rick jones


--
denial, anger, bargaining, depression, acceptance, rebirth...
where do you want to be today?
these opinions are mine, all mine; HP might not want them anyway... :)
feel free to post, OR email to rick.jones2 in hp.com but NOT BOTH...