Sponsored Content
Top Forums UNIX for Advanced & Expert Users AIX: Finding processes attached to shared memory Post 302418888 by DreamWarrior on Wednesday 5th of May 2010 03:38:46 PM
Old 05-05-2010
AIX: Finding processes attached to shared memory

Is there some way to tell what processes are attached to a shared memory segment? We have a system on which I perform "icps -ma" and there are several segments pending deletion having numerous processes attached to them and I can't tell what processes they are. Neither the creator's pid nor last pid that touched them, as listed by ipcs -mp, exist. I'm at a loss.... Is there a command I can execute that will tell me what is attached?
 

10 More Discussions You Might Find Interesting

1. AIX

memory problem in AIX shared libraries

Hi All, I'm facing the following issue with my shared libraries in AIX. memory related calls such as memset, memcpy, malloc etc are failing miserably. there is something wrong with stack/memory which i can't guess. i've used the following flags to build my libraray: ld -G... (0 Replies)
Discussion started by: abhinav05252
0 Replies

2. AIX

finding memory frequency on vio server in aix

is it possible to find out memory frequency(speed) in vio server in aix? Regards Manoj (0 Replies)
Discussion started by: manoj.solaris
0 Replies

3. UNIX for Advanced & Expert Users

finding shared memory

Using pmap, I was able to get a memory map of an Oracle process. It had the following id: 0000000380000000 4194320K rwxsR Converting that Hex ID to decimal gave: 352321658 So, then I did ipcs -am: IPC status from <running system> as of Thu Jun 18 15:43:17 MDT 2009 T ID ... (1 Reply)
Discussion started by: anilj
1 Replies

4. Shell Programming and Scripting

Processes in Shared Memory

Hello , I would like to know how to check if a given process id belongs to particualr shared memory segment . Please help Thanks in advance (3 Replies)
Discussion started by: rmv
3 Replies

5. Shell Programming and Scripting

Discrepancy in finding the top memory consuming processes

When I run 'top' command,I see the following Memory: 32G real, 12G free, 96G swap free Though it shows as 12G free,I am not able to account for processes that consume the rest 20G. In my understanding some process should be consuming atleast 15-16 G but I am not able to find them. Is... (1 Reply)
Discussion started by: prasperl
1 Replies

6. Homework & Coursework Questions

processes and shared memory

Hi again! I have 2 questions ..: How can i create exactly one number of processes ? For example i want to create l*n processes and i tried this: for(i=0;i<l*n;i++){ pid=fork()} But it creates more than l*n Also, i want each child to run another x.c program with 3 command line... (1 Reply)
Discussion started by: giampoul
1 Replies

7. Homework & Coursework Questions

processes and shared memory

Hi again! I have 2 questions ..: How can i create exactly one number of processes ? For example i want to create l*n processes and i tried this: for(i=0;i<l*n;i++){ pid=fork()} But it creates more than l*n Also, i want each child to run another x.c program with 3 command line... (1 Reply)
Discussion started by: giampoul
1 Replies

8. Programming

Shared library with acces to shared memory.

Hello. I am new to this forum and I would like to ask for advice about low level POSIX programming. I have to implement a POSIX compliant C shared library. A file will have some variables and the shared library will have some functions which need those variables. There is one special... (5 Replies)
Discussion started by: iamjag
5 Replies

9. UNIX for Dummies Questions & Answers

Finding the most memory consuming processes in Linux

Platform: Oracle Linux 6.4 To find the most memory consuming processes, I tried the following 2 methods 1. Method1 # ps aux | head -1 ; ps aux | sort -nk +4 | tail -7 USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 95 0.0 0.0 0 0 ? ... (2 Replies)
Discussion started by: kraljic
2 Replies

10. AIX

AIX memory usage by processes

Hi, i have 2 identical web servers using AIX. I use nmon analyser to check their performance. The server A exceeds 20% memory usage for system, 5% for cache and the rest 75% for processes. While, it uses 4% of Paging Space. The server B exceeds 20% for system, 45% for cache and 35% for processes.... (24 Replies)
Discussion started by: dim
24 Replies
ipcs(1) 							   User Commands							   ipcs(1)

NAME
ipcs - report inter-process communication facilities status SYNOPSIS
ipcs [-aAbciJmopqstZ] [-D mtype] [-z zone] DESCRIPTION
The ipcs utility prints information about active inter-process communication facilities. The information that is displayed is controlled by the options supplied. Without options, information is printed in short format for message queues, shared memory, and semaphores that are currently active in the system. OPTIONS
The following options are supported: -m Prints information about active shared memory segments. -q Prints information about active message queues. -s Prints information about active semaphores. If -m, -q, or -s are specified, information about only those indicated is printed. If none of these three is specified, information about all three is printed subject to these options: -a Uses all XCU5 print options. (This is a shorthand notation for -b, -c, -o, -p, and -t.) -A Uses all print options. (This is a shorthand notation for -b, -c, -i, -J, -o, -p, and -t.) -b Prints information on biggest allowable size: maximum number of bytes in messages on queue for message queues, size of segments for shared memory, and number of semaphores in each set for semaphores. See below for meaning of columns in a listing. -c Prints creator's login name and group name. See below. -D mtype Displays, in hexadecimal and ASCII, the contents of all messages of type mtype found on any message queue that the user invok- ing ipcs has permission to read. If mtype is 0, all messages are displayed. If mtype is negative, all messages with type less than or equal to the absolute value of mtype are displayed. (See msgrcv(2) and msgsnap(2)). -i Prints number of ISM attaches to shared memory segments. -J Prints the creator's project. -o Prints information on outstanding usage: number of messages on queue and total number of bytes in messages on queue for message queues and number of processes attached to shared memory segments. -p Prints process number information: process ID of last process to send a message, process ID of last process to receive a mes- sage on message queues, process ID of creating process, and process ID of last process to attach or detach on shared memory segments. See below. -t Prints time information: time of the last control operation that changed the access permissions for all facilities, time of last msgsnd(2) and last msgrcv(2) on message queues, time of last shmat(2) and last shmdt(2) on shared memory (see shmop(2)), time of last semop(2) on semaphores. See below. -z zone Prints information about facilities associated with the specified zone (see zones(5)). The zone can be specified as either a name or a numeric id. The default is to display information about the zone in which the command is executing. Notice that this option is only useful when executing in the global zone. -Z When executing in the global zone, prints information about all zones. Otherwise, prints information about the zone in which the command is executing. The output includes the zone associated with each facility. The column headings and the meaning of the columns in an ipcs listing are given below. The letters in parentheses indicate the options that cause the corresponding heading to appear and "all" means that the heading always appears. Note: These options only determine what informa- tion is provided for each facility; they do not determine which facilities are listed. T (all) Type of the facility: q message queue m shared memory segment s semaphore ID (all) The identifier for the facility entry. KEY (all) The key used as an argument to msgget(2), semget(2), or shmget(2) to create the facility entry. (Note: The key of a shared memory segment is changed to IPC_PRIVATE when the segment has been removed until all processes attached to the segment detach it.) MODE (all) The facility access modes and flags: The mode consists of 11 characters that are interpreted as follows. The first two characters are: R A process is waiting on a msgrcv(2). S A process is waiting on a msgsnd(2). - The corresponding special flag is not set. The next nine characters are interpreted as three sets of three bits each. The first set refers to the owner's permis- sions; the next to permissions of others in the user-group of the facility entry; and the last to all others. Within each set, the first character indicates permission to read, the second character indicates permission to write or alter the facility entry, and the last character is currently unused. The permissions are indicated as follows: r Read permission is granted. w Write permission is granted. a Alter permission is granted. - The indicated permission is not granted. OWNER (all) The login name of the owner of the facility entry. GROUP (all) The group name of the group of the owner of the facility entry. CREATOR (a,A,c) The login name of the creator of the facility entry. CGROUP (a,A,c) The group name of the group of the creator of the facility entry. CBYTES (a,A,o) The number of bytes in messages currently outstanding on the associated message queue. QNUM (a,A,o) The number of messages currently outstanding on the associated message queue. QBYTES (a,A,b) The maximum number of bytes allowed in messages outstanding on the associated message queue. LSPID (a,A,p) The process ID of the last process to send a message to the associated queue. LRPID (a,A,p) The process ID of the last process to receive a message from the associated queue. STIME (a,A,t) The time the last message was sent to the associated queue. RTIME (a,A,t) The time the last message was received from the associated queue. CTIME (a,A,t) The time when the associated entry was created or changed. ISMATTCH (a,i) The number of ISM attaches to the associated shared memory segments. NATTCH (a,A,o) The number of processes attached to the associated shared memory segment. SEGSZ (a,A,b) The size of the associated shared memory segment. CPID (a,A,p) The process ID of the creator of the shared memory entry. LPID (a,A,p) The process ID of the last process to attach or detach the shared memory segment. ATIME (a,A,t) The time the last attach was completed to the associated shared memory segment. DTIME (a,A,t) The time the last detach was completed on the associated shared memory segment. NSEMS (a,A,b) The number of semaphores in the set associated with the semaphore entry. OTIME (a,A,t) The time the last semaphore operation was completed on the set associated with the semaphore entry. PROJECT (J,A) The project name of the creator of the facility entry. ZONE (Z) The zone with which the facility is associated. ENVIRONMENT VARIABLES
See environ(5) for descriptions of the following environment variables that affect the execution of ipcs: LANG, LC_ALL, LC_CTYPE, LC_MES- SAGES, and NLSPATH. TZ Determine the timezone for the time strings written by ipcs. FILES
/etc/group group names /etc/passwd user names ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWipc | +-----------------------------+-----------------------------+ |Interface Stability |Committed | +-----------------------------+-----------------------------+ |Standard |See standards(5). | +-----------------------------+-----------------------------+ SEE ALSO
ipcrm(1), msgget(2), msgids(2), msgrcv(2), msgsnap(2), msgsnd(2), semget(2), semids(2), semop(2), shmctl(2), shmget(2), shmids(2), shmop(2), attributes(5), environ(5), standards(5), zones(5) NOTES
Things can change while ipcs is running. The information it gives is guaranteed to be accurate only when it was retrieved. SunOS 5.11 17 Jan 2008 ipcs(1)
All times are GMT -4. The time now is 08:58 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy