Sponsored Content
Operating Systems Linux How to easily identify socket given a PID on Linux? Post 302995447 by drysdalk on Wednesday 5th of April 2017 07:55:36 PM
Old 04-05-2017
Hi,

My take on this would be that all the socket information is correct. A process can have multiple network connections open simultaneously. It can also contain multiple threads within itself, which can themselves have multiple connections open, and so on. So in this case, the process with PID 32752 has all four of those connections open.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Session PID & socket connection pid

1. If I use an software application(which connects to the database in the server) in my local pc, how many PID should be registered? Would there be PID for the session and another PID for socket connection? 2. I noticed (through netstat) that when I logged in using the my software application,... (1 Reply)
Discussion started by: pcx26
1 Replies

2. UNIX for Dummies Questions & Answers

How to identify who rebooted the linux server

Hi All, Since server is located at remote place so how to identify which user rebooted the server. Is there any way to identify the user. Thanks in advance, Reg, Bache Gowda (1 Reply)
Discussion started by: bache_gowda
1 Replies

3. UNIX for Dummies Questions & Answers

how to find the owner PID of open socket on Solaris9?

Hi all, I am trying to connect the open socket and its owner PID on my Solaris9 system. But it seems not very easy. As netstat is not as powerful as it is on Linux platform, without the "-program" option, and "lsof -i <UDP|TCP>@<hostIP>" won't show the one i want although it lists some... (1 Reply)
Discussion started by: sleepy_11
1 Replies

4. Programming

Help needed linux socket programming in c

Good evening everyone! :) I'm doing a small client / server application for sharing files in C, and I am trying to implement the following: The client of my application sends to the address 255.255.255.255 a message requesting a particular file.In the network there is only one server,... (1 Reply)
Discussion started by: esmeco
1 Replies

5. Linux

how to identify the raid type on Linux?

Hi any idea on why I am getting this? /sbin/mdadm --detail /dev/md0 mdadm: md device /dev/md0 does not appear to be active. thanks. (2 Replies)
Discussion started by: melanie_pfefer
2 Replies

6. What is on Your Mind?

STILL can't buy a Linux PC easily

A few years ago, Dell announced they were selling PCs with Linux (Ubuntu) preinstalled or with no OS installed. It was about time! So a couple years ago I bought the Inspiron 1525n laptop that I'm typing this on with Ubuntu preinstalled. Yea! (Though I immediately wiped Ubuntu and installed... (7 Replies)
Discussion started by: KenJackson
7 Replies

7. UNIX for Advanced & Expert Users

Identify failed disk in Linux RAID

Good Evening, 2 years ago, I set up an Ubuntu file-server for a friend, who is a photograph amateur. Basically, the server offers a software RAID-5 that can be accessed remotely from a MAC. Unfortunately, I didn't labeled the hard drives (i.e. which physical drive corresponds to the /dev/sdX... (2 Replies)
Discussion started by: Loic Domaigne
2 Replies

8. IP Networking

Packets sent from Linux TCP socket

Hello, Our software is using a TCP socket (AF_INET, SOCK_STREAM) to communicate with an Ethernet device. When we send a message, the message object writes itself in full onto the socket's stream buffer before the software invokes send() from socket.h. I'm still researching, but have 2... (1 Reply)
Discussion started by: bix_20002000
1 Replies

9. Shell Programming and Scripting

Identify CPU usage on the Linux server

We are using linux server. We have below script running on the crontab and it send the alert if the cpu usage is above 90%. My question is, the below script tells the CPU usage for one CPU or all CPU in the server? sar 1 1 | sed '$!d' | awk '{printf("%d", $8)}' > $SAR_LOG Please let me... (4 Replies)
Discussion started by: govindts
4 Replies

10. UNIX for Dummies Questions & Answers

Need script for killing Pid in Linux

need script(shell or python) for killing pid in linux (2 Replies)
Discussion started by: roshan9995
2 Replies
accept(2)							System Calls Manual							 accept(2)

Name
       accept - accept a connection on a socket

Syntax
       #include <sys/types.h>
       #include <sys/socket.h>

       accept(s, addr, addrlen)
       int ns, s;
       struct sockaddr *addr;
       int *addrlen;

Description
       The  system call accepts a connection on a socket. The argument s is a socket that has been created with the call, bound to an address with
       the call and is listening for connections after a call.	The system call extracts the first connection on the queue of pending connections,
       creates	a new socket with the same properties of s and allocates a new file descriptor, ns, for the socket.  If no pending connections are
       present on the queue, and the socket is not marked as nonblocking, blocks the caller until a connection	is  present.   If  the	socket	is
       marked  nonblocking  and  no  pending  connections  are present on the queue, returns an error.	The accepted socket, ns, cannot be used to
       accept more connections.  The original socket s remains open.

       The argument addr is a result parameter that is filled in with the address of the connecting entity, as known to the communications  layer.
       The  exact format of the addr parameter is determined by the domain in which the communication is occurring.  The addrlen is a value-result
       parameter; it should initially contain the amount of space pointed to by addr.  On return, addr contains the actual length in bytes of  the
       address returned.  This call is used with connection-based socket types, currently with SOCK_STREAM.

       You can use the call for the purposes of doing an call by selecting the socket for reading.

Return Values
       The call returns -1 on error.  If the call succeeds, it returns a non-negative integer which is a descriptor for the accepted socket.

Diagnostics
       The call fails if:

       [EBADF]	      The descriptor is invalid.

       [ENOTSOCK]     The descriptor references a file, not a socket.

       [EOPNOTSUPP]   The referenced socket is not of type SOCK_STREAM.

       [EFAULT]       The addr parameter is not in a writable part of the user address space.

       [EWOULDBLOCK]  The socket is marked nonblocking and no connections are present to be accepted.

See Also
       bind(2), connect(2), listen(2), select(2), socket(2)

																	 accept(2)
All times are GMT -4. The time now is 06:41 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy