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 OPENDARWIN
network_namespaces
NETWORK_NAMESPACES(7) Linux Programmer's Manual NETWORK_NAMESPACES(7)
NAME
network_namespaces - overview of Linux network namespaces
DESCRIPTION
Network namespaces provide isolation of the system resources associated with networking: network devices, IPv4 and IPv6 protocol stacks, IP
routing tables, firewall rules, the /proc/net directory (which is a symbolic link to /proc/PID/net), the /sys/class/net directory, various
files under /proc/sys/net, port numbers (sockets), and so on.
A physical network device can live in exactly one network namespace. When a network namespace is freed (i.e., when the last process in the
namespace terminates), its physical network devices are moved back to the initial network namespace (not to the parent of the process).
A virtual network (veth(4)) device pair provides a pipe-like abstraction that can be used to create tunnels between network namespaces, and
can be used to create a bridge to a physical network device in another namespace. When a namespace is freed, the veth(4) devices that it
contains are destroyed.
Use of network namespaces requires a kernel that is configured with the CONFIG_NET_NS option.
SEE ALSO
nsenter(1), unshare(1), clone(2), veth(4), proc(5), sysfs(5), namespaces(7), user_namespaces(7), brctl(8), ip(8), ip-address(8), ip-
link(8), ip-netns(8), iptables(8), ovs-vsctl(8)
COLOPHON
This page is part of release 4.15 of the Linux man-pages project. A description of the project, information about reporting bugs, and the
latest version of this page, can be found at https://www.kernel.org/doc/man-pages/.
Linux 2018-02-02 NETWORK_NAMESPACES(7)