03-01-2013
You need lsof to see pids and ports, generally speaking. Some OS have network artifacts in a per proc directory subtree like /proc/$PID/, so you can find the port there through an entry name. The ps can show you the command line, but that does not have to reveal any socket ports.
10 More Discussions You Might Find Interesting
1. IP Networking
I am trying to connect via DBACCESS and Informix server to a server on a different computer. When I execute the connect command from dbaccess I get the following message,
Exec format error cannot bind a name to the port.
As far as I know the port is not being used by another client.
How... (1 Reply)
Discussion started by: lopez
1 Replies
2. UNIX for Dummies Questions & Answers
Hi All, I suspect this is simple but I cannot find any info on it.
I have a logfile on a solaris box (EMS) that I want to tail -f but I want the output of this to be redirected to a TCP port.
I have a second solaris box (PEM) running patrol enterprise manager that I am using as an alarm... (1 Reply)
Discussion started by: mscomms
1 Replies
3. UNIX for Dummies Questions & Answers
Hi
Is there any way to restrict the TCP-IP port usage.
I want to restrict TCP-IP port 1500/1550 to the oracle osuser.
Tanks in advance.
Remi (2 Replies)
Discussion started by: remivisser
2 Replies
4. Solaris
Hi all
I haven't had much experience with Solaris 10 but we've started running into a problem where a process hangs, it is killed and leaves a zombie process. The sysadmins are saying this zombie process is locking a tcp port and not allowing the process to start up.
The process is a usually... (5 Replies)
Discussion started by: casphar
5 Replies
5. UNIX for Dummies Questions & Answers
Hello, I have a service running (ODBC) and every now and then it will hang and I will have to stop and restart the service. The problem is when I stop the service, it indeed stops the service, but netstat reports a tcp port still open with the fin_wait_2 status. Then I must close the client... (1 Reply)
Discussion started by: raidzero
1 Replies
6. IP Networking
Hi. I ran nmap on my server, and I get the following:
Starting Nmap 4.76 ( http://nmap.org ) at 2009-03-19 16:33 EDT
Interesting ports on -------- (-----):
Not shown: 997 closed ports
PORT STATE SERVICE
22/tcp open ssh
80/tcp open http
6881/tcp open bittorrent-tracker
The... (0 Replies)
Discussion started by: Rledley
0 Replies
7. Shell Programming and Scripting
I have multiple processes running the same program on my linux machine. For each process I want to be able to use a unique (available) TCP port. I have thought of using netstat to check which ports are available for use however, the time-window between checking and selecting might expose some race... (1 Reply)
Discussion started by: timmylita
1 Replies
8. UNIX for Advanced & Expert Users
Hey guys,
I need to kill the process that is currently connected to port 10540. I'm on HP-UX machine.
Below is the result of my netstat.
$ netstat -an |grep 10540
tcp 0 0 129.0.0.1.10540 *.* LISTEN
We don't have lsof command, but we have fuser.
... (3 Replies)
Discussion started by: brichigo
3 Replies
9. Programming
Hello,
I'm trying to write a small c application to test a tcp port. This works fine for the most part but the default timeout on the connect is very long. I have been reading many posts but and it looks like I need to set the socket to be non-blocking and poll for a result. I have been totally... (2 Replies)
Discussion started by: tjones1105
2 Replies
10. Solaris
please find the below o/p for your reference
bash-3.00# fcinfo hba-port
HBA Port WWN: 21000024ff295a34
OS Device Name: /dev/cfg/c2
Manufacturer: QLogic Corp.
Model: 375-3356-02
Firmware Version: 05.03.02
FCode/BIOS Version: BIOS: 2.02; fcode: 2.01;... (3 Replies)
Discussion started by: sb200
3 Replies
LEARN ABOUT FREEBSD
sockstat
SOCKSTAT(1) BSD General Commands Manual SOCKSTAT(1)
NAME
sockstat -- list open sockets
SYNOPSIS
sockstat [-46cLlu] [-j jid] [-p ports] [-P protocols]
DESCRIPTION
The sockstat command lists open Internet or UNIX domain sockets.
The following options are available:
-4 Show AF_INET (IPv4) sockets.
-6 Show AF_INET6 (IPv6) sockets.
-c Show connected sockets.
-j jid Show only sockets belonging to the specified jail ID.
-L Only show Internet sockets if the local or foreign addresses are not in the loopback network prefix 127.0.0.0/8, or do not con-
tain the IPv6 loopback address ::1.
-l Show listening sockets.
-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 protocols
Only show sockets of the specified protocols. The protocols argument is a comma-separated list of protocol names, as they are
defined in protocols(5).
-u Show AF_LOCAL (UNIX) sockets.
If neither -4, -6 or -u is specified, sockstat will list sockets in all three domains.
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)).
If a socket is associated with more than one file descriptor, it is shown multiple times. If a socket is not associated with any file
descriptor, the first four columns have no meaning.
SEE ALSO
fstat(1), netstat(1), procstat(1), inet(4), inet6(4), 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>.
BSD
May 16, 2012 BSD