#include <unistd.h>
#include <sys/types.h>
#include <sys/ipc.h>
#include <sys/shm.h>
#include <stdio.h>
#include <stdlib.h>
void die(const char *msg)
{
perror(msg);
exit(1);
}
int main() {
int a=5,b=7;
key_t keyshm; // or key_t keyshm=0x200;
keyshm=ftok("/tmp",32); //see up
int buffer[1];
int *point;
int shmid;
shmid=shmget(keyshm , sizeof(buffer),0666);
if(shmid < 0) die("Couldn't shmget");
point=(int *)shmat(shmid,NULL,0);
point[0]=a;
point[1]=b;
printf("FIRST = %d\nSECOND = %d",point[0],point[1]);
fflush(stdout);
sleep(300);
shmdt(point);
exit(0);
}
Code:
$ ./shm1
Couldn't shmget: No such file or directory
$ man shmget
SHMGET(2) Linux Programmer's Manual SHMGET(2)
...
ERRORS
On failure, errno is set to one of the following:
EACCES The user does not have permission to access the shared memory
segment, and does not have the CAP_IPC_OWNER capability.
EEXIST IPC_CREAT | IPC_EXCL was specified and the segment exists.
EINVAL A new segment was to be created and size < SHMMIN or size > SHM-
MAX, or no new segment was to be created, a segment with given
key existed, but size is greater than the size of that segment.
ENFILE The system limit on the total number of open files has been
reached.
ENOENT No segment exists for the given key, and IPC_CREAT was not spec-
ified.
ENOMEM No memory could be allocated for segment overhead.
ENOSPC All possible shared memory IDs have been taken (SHMMNI), or
allocating a segment of the requested size would cause the sys-
tem to exceed the system-wide limit on shared memory (SHMALL).
EPERM The SHM_HUGETLB flag was specified, but the caller was not priv-
ileged (did not have the CAP_IPC_LOCK capability).
...
So you want 0666 | IPC_CREAT
And you should check the return values of everything in case anything you weren't expecting fails.
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)
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)
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)
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)
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)
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)
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)
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
LEARN ABOUT OPENDARWIN
shmget
SHMGET(2) BSD System Calls Manual SHMGET(2)NAME
shmget -- get shared memory area identifier
SYNOPSIS
#include <sys/types.h>
#include <sys/ipc.h>
#include <sys/shm.h>
int
shmget(key_t key, int size, int shmflg);
DESCRIPTION
shmget() returns the shared memory identifier associated with the key key.
A shared memory segment is created if either key is equal to IPC_PRIVATE, or key does not have a shared memory segment identifier associated
with it, and the IPC_CREAT bit is set in shmflg.
If a new shared memory segment is created, the data structure associated with it (the shmid_ds structure, see shmctl(2)) is initialized as
follows:
o shm_perm.cuid and shm_perm.uid are set to the effective uid of the calling process.
o shm_perm.gid and shm_perm.cgid are set to the effective gid of the calling process.
o shm_perm.mode is set to the lower 9 bits of shmflg.
o shm_lpid, shm_nattch, shm_atime, and shm_dtime are set to 0
o shm_ctime is set to the current time.
o shm_segsz is set to the value of size.
RETURN VALUES
Upon successful completion a positive shared memory segment identifier is returned. Otherwise, -1 is returned and the global variable errno
is set to indicate the error.
ERRORS
[EACESS] A shared memory segment is already associated with key and the caller has no permission to access it.
[EEXIST] Both IPC_CREAT and IPC_EXCL are set in shmflg, and a shared memory segment is already associated with key.
[ENOSPC] A new shared memory indentifier could not be created because the system limit for the number of shared memory identifiers
has been reached.
[ENOENT] IPC_CREAT was not set in shmflg and no shared memory segment associated with key was found.
[ENOMEM] There is not enough memory left to created a shared memory segment of the requested size.
SEE ALSO shmctl(2), shmat(2), shmdt(2)BSD August 17, 1995 BSD