PCP - maps ports to PIDs

6 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Get all associated pids

im looking for a portable way to get the PID of the script that is running, and to get every other PIDs that are spawned from it. and by ever other PIDs, i presume, that would be "child processes". however, i want to shy away from using any command that is not available on every single unix...

2. Shell Programming and Scripting

Need help to kill pids

Hi there !!! I am writing a script to kill the pids on different linux boxes :cool: the output of my command gives the pids running on that box, but how can I kill all the pids without looping? :confused: Code: ssh $i ps -fu $USER | grep ManServer | grep -v grep | awk '{print $2}' | kill ...

3. UNIX for Dummies Questions & Answers

/proc/pid/maps

I think the libc.so is shared between processes, because it is a shared library and OS is engaged for saving memory. But, below, the maps of bash, shows r-xp and r--p rw-p attributes to libc.so which mean private memory space. Can anybody explain this for me? :)cat /proc/$$/maps...

4. Solaris

Conflict with PIDs

I am trying to determine the root cause of a java process that dies trying to startup during it's cron job. I did go ahead and change the time that it starts up in the cron file and now it starts successfully. However is there a way to determine what PID a process was attempting to get when...

5. Red Hat

read maps from /proc/pid/

hi, i hav a query abt reading the contents of /proc/pid/maps file.is there any system apis or functions available to get the data from dat file and parse according to my need. i need name of the .so,Create date of the .so file.,Location of .so file etc. please provide a good source. yes i hav...

6. UNIX for Advanced & Expert Users

NIS Maps

Hello.. I stink at NIS! :) Im having a problem with NIS on solaris 2.X. / SPARC I have some maps that are exported to all clients in the domain. Now I setup a new server and add it as a nis client to the domain. On the NIS server there is a auto_direct map that mounts /usr/local . This is...

LEARN ABOUT OPENDARWIN

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

Solaris BigAdmin RSS