Shared memory with curses Post: 302089184

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

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

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

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

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

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

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.

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:

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?

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

LEARN ABOUT NETBSD

msgget

MSGGET(2)						      BSD System Calls Manual							 MSGGET(2)

NAME

     msgget -- get message queue identifier

LIBRARY

     Standard C Library (libc, -lc)

SYNOPSIS

     #include <sys/msg.h>

     int
     msgget(key_t key, int msgflg);

DESCRIPTION

     The msgget() system call returns the message queue identifier associated with key.  A message queue identifier is a unique integer greater
     than zero.

     A message queue is created if either key is equal to IPC_PRIVATE, or key does not have a message queue identifier associated with it and the
     IPC_CREAT bit is set in msgflg.  If both the IPC_CREAT bit and the IPC_EXCL bit are set in msgflg, and key has a message queue identifier
     associated with it already, the operation will fail.

     If a new message queue is created, the data structure associated with it (the msqid_ds structure, see msgctl(2)) is initialized as follows:

     o	 msg_perm.cuid and msg_perm.uid are set to the effective uid of the calling process.

     o	 msg_perm.gid and msg_perm.cgid are set to the effective gid of the calling process.

     o	 msg_perm.mode is set to the lower 9 bits of msgflg.

     o	 msg_qnum, msg_lspid, msg_lrpid, msg_rtime, and msg_stime are set to 0.

     o	 msg_qbytes is set to the system wide maximum value for the number of bytes in a queue (MSGMNB).

     o	 msg_ctime is set to the current time.

RETURN VALUES

     Upon successful completion a positive message queue identifier is returned.  Otherwise, -1 is returned and the global variable errno is set
     to indicate the error.

ERRORS

     [EACCES]		A message queue is already associated with key and the caller has no permission to access it.

     [EEXIST]		Both IPC_CREAT and IPC_EXCL are set in msgflg, and a message queue is already associated with key.

     [ENOSPC]		A new message queue could not be created because the system limit for the number of message queues has been reached.

     [ENOENT]		IPC_CREAT is not set in msgflg and no message queue associated with key was found.

SEE ALSO

     msgctl(2), msgrcv(2), msgsnd(2), ftok(3)

STANDARDS

     The msgget system call conforms to X/Open System Interfaces and Headers Issue 5 (``XSH5'').

HISTORY

     Message queues appeared in the first release of AT&T System V UNIX.

BSD
								   May 13, 2004 							       BSD

10 More Discussions You Might Find Interesting

1. Programming

Shared memory

Discussion started by: joseph_shibu

2. UNIX for Advanced & Expert Users

Shared memory shortage but lots of unused memory

Discussion started by: cjcamaro

3. Linux

all about shared memory

Discussion started by: vijaya2006

4. Programming

help with shared memory

Discussion started by: ddx08