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 CENTOS

pcp.conf

PCP.CONF(5)							File Formats Manual						       PCP.CONF(5)

NAME

       pcp.conf - the Performance Co-Pilot configuration and environment file

SYNOPSIS

       /etc/pcp.conf

DESCRIPTION

       When  using  Performance Co-Pilot (PCP) tools and utilities and when calling PCP library functions, a standard set of environment variables
       are defined in /etc/pcp.conf.  These variables are generally used to specify the location of various PCP pieces in the file system and  may
       be  loaded  into  shell scripts by sourcing the /etc/pcp.env(5) shell script and queried by C/C++ programs using the pmGetConfig(3) library
       function.  If a variable is already defined in the environment, the values in pcp.conf do not override those values,  i.e.  the	values	in
       pcp.conf serve as installation defaults only.

       Both  the  pcp.env  and	pcp.conf  files  are expected to be found in /etc by default.  If required, the pcp.conf file may be relocated and
       PCP_CONF set in the environment to specify the full path to the new location.  The pcp.env file can not be relocated (this is the only hard
       coded path required by PCP).

       The syntax rules for pcp.conf are as follows :

       1.  the general syntax is
						       PCP_VARIABLE_NAME=variable value to end of line

       2.  lines that begin with # and all blank lines are ignored.

       3.  all variables must be prefixed with PCP_.  This is a security issue - variables that do not have this prefix will be silently ignored.

       4.  there  should  be  no  space  between the variable name and the literal = and no space between the = and the variable value (unless the
	   value actually starts with a space).  This is required because the pcp.conf file may be sourced directly by Makefiles as well as inter-
	   preted by the pcp.env script and the pmGetConfig function.

       5.  variable  values  may  contain  spaces  and should not be quoted.  The pcp.env script automatically quotes all variable values from the
	   character immediately following the = through to the end of the line.

       For further details and an explanation of the use of each variable, see the comments in the /etc/pcp.conf file itself.

ENVIRONMENT

       The PCP_CONF environment variable specifies an alternative path to the pcp.conf file.

SEE ALSO

       PCPIntro(1), PCPIntro(3), PMAPI(3), pmGetConfig(3) and pcp.env(5).

Performance Co-Pilot							PCP							       PCP.CONF(5)

Solaris BigAdmin RSS