10-06-2012
Bound, Unbound, Idle, Listening,
Hi Guys,
I am studying netstat and I am getting confused a lot. I will be glad if someone will be kind enough to explain to me :
1) bound port
2) unbound port
3) idle
4 listening
I will very much appreciate it. Thanks guys
Moderator's Comments:
|
|
We have a special forum with special rules for homework
|
|
Last edited by jim mcnamara; 10-06-2012 at 06:37 PM..
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 DEBIAN
sockstat
SOCKSTAT(1) BSD General Commands Manual SOCKSTAT(1)
NAME
sockstat -- list open sockets
SYNOPSIS
sockstat [-clh] [-p ports] [-P pid|process] [-U uid|user] [-G gid|group]
DESCRIPTION
The sockstat command lists open Internet or UNIX domain sockets.
The following options are available:
-c Show connected sockets.
-l Show listening sockets.
-h Show a usage summary.
-p ports Only show Internet sockets if either the local or foreign port number is on the specified list. The ports argument is a comma-
separated list of port numbers and ranges specified as first and last port separated by a dash.
-P pid|process
Only show sockets of the specified pid|process. The pid|process argument is a process name or pid.
-U uid|user
Only show sockets of the specified uid|user. The uid|user argument is a username or uid.
-G gid|group
Only show sockets of the specified gid|group. The gid|group argument is a groupname or gid.
If neither -c or -l is specified, sockstat will list both listening and connected sockets.
The information listed for each socket is:
USER The user who owns the socket.
COMMAND The command which holds the socket.
PID The process ID of the command which holds the socket.
FD The file descriptor number of the socket.
PROTO The transport protocol associated with the socket for Internet sockets, or the type of socket (stream or datagram) for UNIX
sockets.
LOCAL ADDRESS For Internet sockets, this is the address the local end of the socket is bound to (see getsockname(2)). For bound UNIX
sockets, it is the socket's filename. For other UNIX sockets, it is a right arrow followed by the endpoint's filename, or
``??'' if the endpoint could not be determined.
FOREIGN ADDRESS (Internet sockets only) The address the foreign end of the socket is bound to (see getpeername(2)).
SEE ALSO
netstat(1), protocols(5)
HISTORY
The sockstat command appeared in FreeBSD 3.1.
AUTHORS
The sockstat command and this manual page were written by Dag-Erling Smorgrav <des@FreeBSD.org>.
The sockstat command was ported to Linux by William Pitcock <nenolod@nenolod.net>.
BSD
May 18, 2008 BSD