05-06-2010
Quote:
Originally Posted by
helltrex
What if the operating systems would not use any ipc mechanism in order to exchange the datas with each other,which technique could be an alternative for messaging between the processes? Do you guys think using the vfork () system call to duplicate processes is a logical solution for this problem?
vfork hardly seems a solution to the problem of communication in general. If IPC is unavailable, it's possible to create ad-hoc mutexes with temp files: open("/tmp/lockfile", O_CREAT|O_EXCL, 000) will only succeed for the process that gets to create the file. You could also exploit the queueing behavior of fifos. Or you could use sockets.
8 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
Hi,
The description and the context of the mechanism that i require is as follows:
There is an application communicating with a protocol stack binary. There is a TCP socket communication between the two.
Now, the stack is pumping up data to the Application such that the receiving buffer of... (2 Replies)
Discussion started by: saptarshi
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. Shell Programming and Scripting
I have a shell script.
How can use some kind of locking mechanism to ensure that the script is not being executed by two people
at the same time? (3 Replies)
Discussion started by: tjay83
3 Replies
5. AIX
Hi all,
on aix,whether have udev or devfs mechanism?
thanks! (4 Replies)
Discussion started by: anonys
4 Replies
6. Programming
OIOIC is a completely new object-oriented mechanism for the C programming language.
Please download the "OIOIC-Primer-2nd-Edition-English.tar.gz". (the English version of << OIOIC Primer >> )
http://code.google.com/p/oioic/downloads/list
Welcome your advice!
Using OIOIC, you can describe... (7 Replies)
Discussion started by: pervise.zhao
7 Replies
7. 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
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
LEARN ABOUT DEBIAN
zmq_ipc
ZMQ_IPC(7) 0MQ Manual ZMQ_IPC(7)
NAME
zmq_ipc - 0MQ local inter-process communication transport
SYNOPSIS
The inter-process transport passes messages between local processes using a system-dependent IPC mechanism.
Note
The inter-process transport is currently only implemented on operating systems that provide UNIX domain sockets.
ADDRESSING
A 0MQ address string consists of two parts as follows: transport://endpoint. The transport part specifies the underlying transport protocol
to use, and for the inter-process transport shall be set to ipc. The meaning of the endpoint part for the inter-process transport is
defined below.
Assigning a local address to a socket
When assigning a local address to a socket using zmq_bind() with the ipc transport, the endpoint shall be interpreted as an arbitrary
string identifying the pathname to create. The pathname must be unique within the operating system namespace used by the ipc
implementation, and must fulfill any restrictions placed by the operating system on the format and length of a pathname.
Connecting a socket
When connecting a socket to a peer address using zmq_connect() with the ipc transport, the endpoint shall be interpreted as an arbitrary
string identifying the pathname to connect to. The pathname must have been previously created within the operating system namespace by
assigning it to a socket with zmq_bind().
WIRE FORMAT
Not applicable.
EXAMPLES
Assigning a local address to a socket.
/* Assign the pathname "/tmp/feeds/0" */
rc = zmq_bind(socket, "ipc:///tmp/feeds/0");
assert (rc == 0);
Connecting a socket.
/* Connect to the pathname "/tmp/feeds/0" */
rc = zmq_connect(socket, "ipc:///tmp/feeds/0");
assert (rc == 0);
SEE ALSO
zmq_bind(3) zmq_connect(3) zmq_inproc(7) zmq_tcp(7) zmq_pgm(7) zmq(7)
AUTHORS
This manual page was written by the 0MQ community.
0MQ 2.2.0 04/04/2012 ZMQ_IPC(7)