09-24-2012
Quote:
Originally Posted by
Corona688
Copying and moving are done by simply opening and writing to files.
What do you wish to use IPC for here?
Actually i am not planning to use IPC here.Its just that i really want to try some application that makes use of both IPC and pthreads
5 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. Programming
how about asynchronous canceling?
or with signal?
if with signal whether it effects the process?
my english so badly :( :( (1 Reply)
Discussion started by: alan.zhao
1 Replies
3. 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
4. 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
5. 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
IPC(2) Linux Programmer's Manual IPC(2)
NAME
ipc - System V IPC system calls
SYNOPSIS
int ipc(unsigned int call, int first, int second, int third,
void *ptr, long fifth);
DESCRIPTION
ipc() is a common kernel entry point for the System V IPC calls for messages, semaphores, and shared memory. call determines which IPC
function to invoke; the other arguments are passed through to the appropriate call.
User programs should call the appropriate functions by their usual names. Only standard library implementors and kernel hackers need to
know about ipc().
CONFORMING TO
ipc() is Linux-specific, and should not be used in programs intended to be portable.
NOTES
On a few architectures, for example ia64, there is no ipc() system call; instead msgctl(2), semctl(2), shmctl(2), and so on really are
implemented as separate system calls.
SEE ALSO
msgctl(2), msgget(2), msgrcv(2), msgsnd(2), semctl(2), semget(2), semop(2), semtimedop(2), shmat(2), shmctl(2), shmdt(2), shmget(2)
COLOPHON
This page is part of release 3.27 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 2007-06-28 IPC(2)