10-08-2012
A socket can be in various states (bound to an address/port, unbound, listening, idle, etc.)
Other than ESTABLISHED, here are some other possible states that netstat can output:
Quote:
BOUND Bound, ready to connect or listen.
UNBOUND Not waiting for anything,
CLOSED Closed. The socket is not being used.
CLOSING Closed, then remote shutdown; awaiting acknowledgment.
CLOSE_WAIT Remote shutdown; waiting for the socket to close.
FIN_WAIT_1 Socket closed; shutting down connection.
FIN_WAIT_2 Socket closed; waiting for shutdown from remote.
IDLE Idle, opened but not bound.
LAST_ACK Remote shutdown, then closed; awaiting acknowledgment.
LISTEN Listening for incoming connections.
SYN_RECEIVED Initial synchronization of the connection under way.
SYN_SENT Actively trying to establish connection.
TIME_WAIT Wait after close for remote shutdown retransmission.
This User Gave Thanks to fpmurphy For This Post:
8 More Discussions You Might Find Interesting
1. What is on Your Mind?
Hi guys, lets make this more interesting... I'm sure you listen to something when your working on a project or something... I know, I do, helps with concentration.
Track: ±¯¸èÖ®Íõ (King of sad songs)
Artist: -îǧ‹Ã Miriam Yeung
Lovely forum BTW! :D (33 Replies)
Discussion started by: hype.it
33 Replies
2. What is on Your Mind?
This is has been posted many times before... It is not in this forum as of now, so I have decided to put it here :D
I'm listening to The Outsiders (AKA Hell is for Heros Part I) by Modern Life is War.... what about ya'll? (4 Replies)
Discussion started by: Mars8082686
4 Replies
3. Solaris
How to get the list of zones which are bound to a pool say appPool. Rather then logging in each zone and then check from pool stat command. (3 Replies)
Discussion started by: fugitive
3 Replies
4. Programming
I was trying to test dump data on bedework jxi console however I got the error below.I'm using debian as my OS and installed quickstart bedework on it. Pls advise what am I missing. thanks
Caused by: javax.naming.NameNotFoundException: env not bound
at... (1 Reply)
Discussion started by: lhareigh890
1 Replies
5. Linux
Hi all,
Am getting the below error for a job that is run in our system.
error code: 114, pc=0, call=1, seg=0
114 Attempt to access item beyond bounds of memory (Signal 11)
This job uses a cobol program and as far as I know, the problem is related to this cobol program.
What does this... (1 Reply)
Discussion started by: das.somik
1 Replies
6. High Performance Computing
I want to build a computing cluster and have been looking into grid solutions. My understanding from grid solutions is that participating nodes have to actually sign up to participate in a computation and that an isolated piece of work is sent to the node through a request from that node (pull).... (4 Replies)
Discussion started by: figaro
4 Replies
7. Emergency UNIX and Linux Support
Hi All,
Can you please answer my question.
i see lot of CPU utilization on AIX LPARs. i am able to find the cause of the probelm. But i do not know how to mitigate or fix the problem.
for instance,
i found the process which is consuming most of CPU. i informed the responsible team.
how... (7 Replies)
Discussion started by: System Admin 77
7 Replies
8. Shell Programming and Scripting
Hi all,
I've data as:
22 51018157 51018157 exonic CHKB nonsynonymous SNV
22 51018204 51018204 exonic CHKB nonsynonymous SNV
22 51018428 51018428 exonic CHKB nonsynonymous SNV
22 51018814 51018814 ... (4 Replies)
Discussion started by: genome
4 Replies
LEARN ABOUT REDHAT
ssl_get_shutdown
SSL_set_shutdown(3) OpenSSL SSL_set_shutdown(3)
NAME
SSL_set_shutdown, SSL_get_shutdown - manipulate shutdown state of an SSL connection
SYNOPSIS
#include <openssl/ssl.h>
void SSL_set_shutdown(SSL *ssl, int mode);
int SSL_get_shutdown(SSL *ssl);
DESCRIPTION
SSL_set_shutdown() sets the shutdown state of ssl to mode.
SSL_get_shutdown() returns the shutdown mode of ssl.
NOTES
The shutdown state of an ssl connection is a bitmask of:
0 No shutdown setting, yet.
SSL_SENT_SHUTDOWN
A "close notify" shutdown alert was sent to the peer, the connection is being considered closed and the session is closed and correct.
SSL_RECEIVED_SHUTDOWN
A shutdown alert was received form the peer, either a normal "close notify" or a fatal error.
SSL_SENT_SHUTDOWN and SSL_RECEIVED_SHUTDOWN can be set at the same time.
The shutdown state of the connection is used to determine the state of the ssl session. If the session is still open, when SSL_clear(3) or
SSL_free(3) is called, it is considered bad and removed according to RFC2246. The actual condition for a correctly closed session is
SSL_SENT_SHUTDOWN (according to the TLS RFC, it is acceptable to only send the "close notify" alert but to not wait for the peer's answer,
when the underlying connection is closed). SSL_set_shutdown() can be used to set this state without sending a close alert to the peer (see
SSL_shutdown(3)).
If a "close notify" was received, SSL_RECEIVED_SHUTDOWN will be set, for setting SSL_SENT_SHUTDOWN the application must however still call
SSL_shutdown(3) or SSL_set_shutdown() itself.
RETURN VALUES
SSL_set_shutdown() does not return diagnostic information.
SSL_get_shutdown() returns the current setting.
SEE ALSO
ssl(3), SSL_shutdown(3), SSL_CTX_set_quiet_shutdown(3), SSL_clear(3), SSL_free(3)
0.9.7a 2001-08-20 SSL_set_shutdown(3)