Sponsored Content
Top Forums Programming Shared memory between two c program Post 302584307 by Corona688 on Thursday 22nd of December 2011 06:12:33 PM
Old 12-22-2011
I didn't even run the first one, at all, and your second program didn't bother waiting for it.

Next time I run it, it complains that the shared memory segment already exists. Why are you using IPC_EXCL all the time?

Only one of your programs should be allowed to create the semaphore, in any case.
 

10 More Discussions You Might Find Interesting

1. Programming

Shared memory

Dear Reader, Is is necessary to attach / dettach the shared memory segments for write operations , if more than one program is accessing same shared memory segments.. I have used semaphore mutex and still I'm getting segmentation fault when I write to the segment when other program is already... (1 Reply)
Discussion started by: joseph_shibu
1 Replies

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

3. Linux

all about shared memory

Hi all :confused: , I am new to unix.I have been asked to implement shared memory in user's mode.What does this mean?What is the difference it makes in kernel mode and in users mode?What are the advantages of this impemenation(user's mode)? And also i would like to know why exactly shared... (0 Replies)
Discussion started by: vijaya2006
0 Replies

4. Programming

help with shared memory

what i want to do is have an int that can been written into by 2 processes but my code doesn't seem to work. #include <sys/types.h> #include <sys/ipc.h> #include <sys/sem.h> #include <sys/shm.h> #include<stdio.h> #define KEY1 (1492) int main() { int shmid; volatile int * addr;... (6 Replies)
Discussion started by: ddx08
6 Replies

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

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

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

8. UNIX for Advanced & Expert Users

Shared Memory

Hi, Using ipcs we can see shared memory, etc.. details. How can I add/remove shared memory(command name)? Thanks, Naga:cool: (2 Replies)
Discussion started by: Nagapandi
2 Replies

9. AIX

shared memory

1.How to know wich process is using the shared memory? 2.How to flush (release) the process from the shared memory? (1 Reply)
Discussion started by: pchangba
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 interprocess communication facilities status

Syntax
       ipcs [options]

Description
       The  command  provides  information about active, interprocess communication facilities, message queues, shared memory, and semaphores that
       are currently active in the system.

Options
       The information is displayed in columns and is controlled by the following options:

       -m     Displays information about active shared memory segments

       -q     Displays information about active message queues

       -s     Displays information about active semaphores

       If any of the options -q, -m, or -s are specified, information about only those indicated are printed.  If none of these  three	is  speci-
       fied, information about all three are printed.

       -a     Uses all print options (shorthand notation for -b, -c, -o, -p and -t)

       -b     Displays	the  biggest allowable size information (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)

       -C     Uses the specified core file (next argument) in place of

       -c     Displays creator's login name and group name

       -N     Uses the specified namelist (next argument) in place of

       -o     Displays the outstanding usage information  (number of messages in queue, size of each and number of processes  attached	to  shared
	      memory segments)

       -p     Displays	the  process ID information (process ID of last process to send a message and process ID of last process to receive a mes-
	      sage on message queues and process ID of creating process and process ID of last process to attach or detach on shared  memory  seg-
	      ments)

       -t     Displays	all  time  statistics  (time of the last control operation that changed the access permissions for all facilities, time of
	      last and last on message queues, last and last on shared memory, last on semaphores)

       The column headings and the meaning of the columns in an listing are given below.  The letters in parentheses  indicate	the  options  that
       cause the corresponding heading to appear; all means that the heading always appears.  Note that these options only determine what informa-
       tion is provided for each facility; they do not determine which facilities are listed.

       T (all)		   Type of 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 or 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.	The first two characters are interpreted as follows:

			   R	  If the process is waiting on a

			   S	  If a process is waiting on a

			   D	  If  the  associated shared memory segment has been removed.  It disappears when the last process attached to the
				  segment detaches it.

			   C	  If the associated shared memory segment is to be clear when the first attach is executed.

			   -	  If the corresponding special flag is not set.

			   The next 9 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 write or alter the facility entry, and the last character is cur-
			   rently unused.
			   The permissions are indicated as follows:

			   r	  If read permission is granted

			   w	  If write permission is granted

			   a	  If alter permission is granted

			   -	  If 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,c)	   The login name of the creator of the facility entry.

       CGROUP (a,c)	   The group name of the group of the creator of the facility entry.

       CBYTES (a,o)	   The number of bytes in messages currently outstanding on the associated message queue.

       QNUM (a,o)	   The number of messages currently outstanding on the associated message queue.

       QBYTES (a,b)	   The maximum number of bytes allowed in messages outstanding on the associated message queue.

       LSPID (a,p)	   The process ID of the last process to send a message to the associated queue.

       LRPID (a,p)	   The process ID of the last process to receive a message from the associated queue.

       STIME (a,t)	   The time the last message was sent to the associated queue.

       RTIME (a,t)	   The time the last message was received from the associated queue.

       CTIME (a,t)	   The time the associated entry was created or changed.

       NATTCH (a,o)	   The number of processes attached to the associated shared memory segment.

       SEGSZ (a,b)	   The size of the associated shared memory segment.

       CPID (a,p)	   The process ID of the creator of the shared memory entry.

       LPID (a,p)	   The process ID of the last process to attach or detach the shared memory segment.

       ATIME (a,t)	   The time the last attach was completed to the associated shared memory segment.

       DTIME (a,t)	   The time the last detach was completed on the associated shared memory segment.

       NSEMS (a,b)	   The number of semaphores in the set associated with the semaphore entry.

       OTIME (a,t)	   The time the last semaphore operation was completed on the set associated with the semaphore entry.

Restrictions
       Things can change while is running.  The picture it gives is only a close approximation to reality.

Files
       /vmunix	 system namelist
       /dev/kmem memory
       /etc/passwd    user names
       /etc/group     group names

See Also
       ipcrm(2), msgop(2), semop(2), shmop(2)

																	   ipcs(1)
All times are GMT -4. The time now is 02:57 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy