05-30-2001
The primary way to share data between processes using UNIX IPCs are:
(1) Shared memory;
(2) Sockets:
There are other UNIX IPCs including
(3) Message Queues.
(4) Semaphores;
(5) Signals.
Your best best (for IPCs) is to use shared memory segments, based on your post. You might need to use semaphores to insure that the shared memory operations are atomic.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I have a parent that is passing data to child A and then child A has to process it and pass to child B. I am able to pass the data to child A but am not able to pass it to child B. Child B seems to only be receiving the last data instead of the whole data.
I saw one example in a book but it uses... (1 Reply)
Discussion started by: scmay
1 Replies
2. UNIX for Dummies Questions & Answers
hai,
i am doing my masters degree in computers.please any one tell me about
fork(),semaphores,mutex,messaging queues,messaging using pipes ,and msgget(),msgrecv() funtions
in ipc programming .
i have exam on that i have a book but in that they not given clearly.
hope u will
... (2 Replies)
Discussion started by: G.Vishnuvardhan
2 Replies
3. Programming
Hi! I'm trying to write this program: in my intentions it should get a message and send it to a second process (pid_upost), then to a third process (pid1, pid2, pid3, depending on the choice made when a new message is inserted). This program should write the message in a file (message1, message2 or... (1 Reply)
Discussion started by: Kaminski
1 Replies
4. Programming
Hi guys, I'm new to Linux and Unix I have just simple code . But I don't know why it doesn't work ..
But, the outputfile is Blank.. I don't understand why.. Please help me.. Thank you very much
P.S: sorry, I don't know how to edit this post clearly.. it's hard to read.. Please try.. (2 Replies)
Discussion started by: thanh_sam_khac
2 Replies
5. Solaris
I was asked to look into a problem with a Sun Netra 440 in another department. On the server in question, the relevant 'uname -a' information is, "SunOS host1 5.9 Generic_118558-16 sun4u sparc SUNW,Netra-440". That information aside, while the other admin is logged into the ALOM, these errors are... (0 Replies)
Discussion started by: Borealis
0 Replies
6. Programming
Hi!
I wanted to know the advantages / disadvantages of different IPC mechanims such as sockets, pipes (unnamed) , shared memory & message queues.
Pipes for example i hear are fast , but are difficult to debug as compared to sockets.
Can you guys please name some situations where one is... (4 Replies)
Discussion started by: _korg
4 Replies
7. Programming
I need to write a program which creates some n number of processes first and also creates a fifo for each of them, then it connects to the server and..
I tried creating these processes with fork() in a for loop but it doesn't print out what i write inside the child..
for(int count = 0; count... (7 Replies)
Discussion started by: saman_glorious
7 Replies
8. Programming
Suppose I have 5 independent process divided in two imaginay sets:
set1 set2
---------------------
p1 p3
| |
p2 p4
|
p5
The processes inside each set communicate mutually quite often.
I mean p1 and p2 communicate mutually quite often
Similarly p3, p4 and p5 communicate mutually... (2 Replies)
Discussion started by: rupeshkp728
2 Replies
9. HP-UX
Hi Experts,
Need your help for checking te interprocess communications settings on HP-UX box.
Using ipcs command I am able to view Message queue,semapohores etc, but from that output I m not able to understand how to determine if there is any issue with ipc settings and how to resolve that? (1 Reply)
Discussion started by: sai_2507
1 Replies
10. Shell Programming and Scripting
Actually i am thinking of some usefull application that involves both IPC and pthreads.But i am not quite sure what type of application involves both these together :confused:.
Anyways i am now working on creating a simple featured file manager that can do the following:
Display file name and... (2 Replies)
Discussion started by: ronmaximus
2 Replies
LEARN ABOUT CENTOS
sem_overview
SEM_OVERVIEW(7) Linux Programmer's Manual SEM_OVERVIEW(7)
NAME
sem_overview - overview of POSIX semaphores
DESCRIPTION
POSIX semaphores allow processes and threads to synchronize their actions.
A semaphore is an integer whose value is never allowed to fall below zero. Two operations can be performed on semaphores: increment the
semaphore value by one (sem_post(3)); and decrement the semaphore value by one (sem_wait(3)). If the value of a semaphore is currently
zero, then a sem_wait(3) operation will block until the value becomes greater than zero.
POSIX semaphores come in two forms: named semaphores and unnamed semaphores.
Named semaphores
A named semaphore is identified by a name of the form /somename; that is, a null-terminated string of up to NAME_MAX-4 (i.e., 251)
characters consisting of an initial slash, followed by one or more characters, none of which are slashes. Two processes can operate
on the same named semaphore by passing the same name to sem_open(3).
The sem_open(3) function creates a new named semaphore or opens an existing named semaphore. After the semaphore has been opened,
it can be operated on using sem_post(3) and sem_wait(3). When a process has finished using the semaphore, it can use sem_close(3)
to close the semaphore. When all processes have finished using the semaphore, it can be removed from the system using
sem_unlink(3).
Unnamed semaphores (memory-based semaphores)
An unnamed semaphore does not have a name. Instead the semaphore is placed in a region of memory that is shared between multiple
threads (a thread-shared semaphore) or processes (a process-shared semaphore). A thread-shared semaphore is placed in an area of
memory shared between the threads of a process, for example, a global variable. A process-shared semaphore must be placed in a
shared memory region (e.g., a System V shared memory segment created using shmget(2), or a POSIX shared memory object built created
using shm_open(3)).
Before being used, an unnamed semaphore must be initialized using sem_init(3). It can then be operated on using sem_post(3) and
sem_wait(3). When the semaphore is no longer required, and before the memory in which it is located is deallocated, the semaphore
should be destroyed using sem_destroy(3).
The remainder of this section describes some specific details of the Linux implementation of POSIX semaphores.
Versions
Prior to kernel 2.6, Linux supported only unnamed, thread-shared semaphores. On a system with Linux 2.6 and a glibc that provides the NPTL
threading implementation, a complete implementation of POSIX semaphores is provided.
Persistence
POSIX named semaphores have kernel persistence: if not removed by sem_unlink(3), a semaphore will exist until the system is shut down.
Linking
Programs using the POSIX semaphores API must be compiled with cc -pthread to link against the real-time library, librt.
Accessing named semaphores via the file system
On Linux, named semaphores are created in a virtual file system, normally mounted under /dev/shm, with names of the form sem.somename.
(This is the reason that semaphore names are limited to NAME_MAX-4 rather than NAME_MAX characters.)
Since Linux 2.6.19, ACLs can be placed on files under this directory, to control object permissions on a per-user and per-group basis.
CONFORMING TO
POSIX.1-2001.
NOTES
System V semaphores (semget(2), semop(2), etc.) are an older semaphore API. POSIX semaphores provide a simpler, and better designed inter-
face than System V semaphores; on the other hand POSIX semaphores are less widely available (especially on older systems) than System V
semaphores.
EXAMPLE
An example of the use of various POSIX semaphore functions is shown in sem_wait(3).
SEE ALSO
sem_close(3), sem_destroy(3), sem_getvalue(3), sem_init(3), sem_open(3), sem_post(3), sem_unlink(3), sem_wait(3), pthreads(7)
COLOPHON
This page is part of release 3.53 of the Linux man-pages project. A description of the project, and information about reporting bugs, can
be found at http://www.kernel.org/doc/man-pages/.
Linux 2012-05-13 SEM_OVERVIEW(7)