Sponsored Content
Full Discussion: Processes in Shared Memory
Top Forums Shell Programming and Scripting Processes in Shared Memory Post 302364556 by rmv on Friday 23rd of October 2009 10:28:43 AM
Old 10-23-2009
Yes I realized

I realized that the CPID is the creator process id and from there I could
trace all the active processes that are accessing a particular shared memory segment.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Shared memory shortage but lots of unused memory

I am running HP-UX B.11.11. I'm increasing a parameter for a database engine so that it uses more memory to buffer the disk drive (to speed up performance). I have over 5GB of memory not being used. But when I try to start the DB with the increased buffer parameter I get told. "Not... (1 Reply)
Discussion started by: cjcamaro
1 Replies

2. Programming

how to view loaded shared libraries by running processes in linux

anybody knows how to view loaded shared libraries by running processes in linux enviornment? any command or tool ? thanks a lot (3 Replies)
Discussion started by: princelinux
3 Replies

3. Programming

memory sharing - not shared memory -

hi, this is the problem: i want to swap a linked list between 4 processes (unrelated), is there any way i can do that just by sending a pointer to a structure? //example typedef struct node { int x; char c; struct node *next; } node; or i should send the items ( x,c ) by... (9 Replies)
Discussion started by: elzalem
9 Replies

4. Programming

Shared memory in shared library

I need to create a shared library to access an in memory DB. The DB is not huge, but big enough to make it cumbersome to carry around in every single process using the shared library. Luckily, it is pretty static information, so I don't need to worry much about synchronizing the data between... (12 Replies)
Discussion started by: DreamWarrior
12 Replies

5. Programming

Shared memory for shared library

I am writing a shared library in Linux (but compatible with other UNIXes) and I want to allow multiple instances to share a piece of memory -- 1 byte is enough. What's the "best" way to do this? I want to optimize for speed and portability. Obviously, I'll have to worry about mutual exclusion. (0 Replies)
Discussion started by: otheus
0 Replies

6. UNIX for Advanced & Expert Users

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... (7 Replies)
Discussion started by: DreamWarrior
7 Replies

7. Shell Programming and Scripting

Parallel processes to INC- and DEC-rement shared counter

QUESTION: How do I run processes in parallel, so that the counter (in counter.txt) would vary in value (instead of just "0" and "1")? That is, how to not sequentially run inc.sh and dec.sh? The shared counter (a single number starting as 0) is in a file counter.txt. counter.sh is (supposed to... (2 Replies)
Discussion started by: courteous
2 Replies

8. 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

9. 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

10. 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
ipcs(1) 						      General Commands Manual							   ipcs(1)

NAME
ipcs - report status of interprocess communication facilities SYNOPSIS
core] namelist] DESCRIPTION
displays certain information about active interprocess communication facilities. With no options, displays information in short format for the message queues, shared memory segments, and semaphores that are currently active in the system. Options The following options restrict the display to the corresponding facilities. (none) This is equivalent to Display information about active shared memory segments. Display information about active message queues. Display information about active semaphores. The following options add columns of data to the display. See "Column Description" below. (none) Display default columns: for all facilities: Display all columns, as appropriate. This is equivalent to Display largest-allowable-size information: for message queues: for shared memory segments: for semaphores: Display creator's login name and group name: for all facilities: Display information on outstanding usage: for message queues: for shared memory segments: Display process number information: for message queues: for shared memory segments: Display time information: for all facilities: for message queues: for shared memory segments: for semaphores: The following options redefine the sources of information. Use core in place of core can be a core file or a directory created by or Use file namelist or the namelist within core in place of It opens a crash dump for reading. Please refer to cr_open(3) for more details. Column Descriptions The column headings and the meaning of the columns in an listing are given below. The columns are printed from left to right in the order shown below. Facility type: Shared memory segment Message queue Semaphore The identifier for the facility entry. The key used as an argument to or to create the facility entry. (Note: The key of a shared memory segment is changed to when the segment has been removed until all processes attached to the segment detach it.) The facility access modes and flags: The mode consists of 11 characters that are interpreted as follows: The first two characters can be: A process is waiting on a A process is waiting on a The associated shared memory segment has been removed. It will disappear when the last process attached to the segment detaches it. The associated shared memory segment is to be cleared when the first attach is executed. The corresponding special flag is not set. The next 9 characters are interpreted as three sets of three characters each. The first set refers to the owner's permissions, the next to permissions of others in the 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. Read permission is granted. Write permission is granted. Alter permission is granted. The indicated permission is not granted. The login name of the owner of the facility entry. The group name of the group of the owner of the facility entry. The login name of the creator of the facility entry. The group name of the group of the creator of the facility entry. The number of bytes in messages currently outstanding on the associated message queue. The number of messages currently outstanding on the associated message queue. The maximum number of bytes allowed in messages outstanding on the associated message queue. The process ID of the last process to send a message to the associated message queue. The process ID of the last process to receive a message from the associated message queue. The time the last message was sent to the associated message queue. The time the last message was received from the associated message queue. The time when the associated facility entry was created or changed. The number of processes attached to the associated shared memory segment. The size of the associated shared memory segment. The process ID of the creating process of the shared memory segment. The process ID of the last process to attach or detach the shared memory segment. The time the last attach was completed to the associated shared memory segment. The time the last detach was completed on the associated shared memory segment. The number of semaphores in the set associated with the semaphore entry. The time the last semaphore operation was completed on the set associated with the semaphore entry. WARNINGS
produces only an approximate indication of actual system status because system processes are continually changing while is acquiring the requested information. Do not rely on the exact field widths and spacing of the output, as these will vary depending on the system, the release of HP-UX, and the data to be displayed. FILES
Kernel virtual memory Group names User names System namelist SEE ALSO
msgop(2), semop(2), shmop(2). STANDARDS CONFORMANCE
ipcs(1)
All times are GMT -4. The time now is 12:32 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy