Inter process Communication Mechanism

Question

Illustrates about the Inter process Communication Mechanism?

Answer 1

Inter process Communication Mechanism:

• Signals-Unix supports other, very easy communication mechanism-the signal.

• A signal is simple since it does not pass data beyond the continuation of the signal itself.

• Signals in UML: A UML signal is in fact a generalization of the UNIX signal. Whereas a UNIX signal carries no parameters but a condition code, a UML signal is a thing.

• Shared Memory Communication-theoretically, such semaphores are the mechanism we employ to make shared memory safe.

• POSIX assists semaphores, but this also supports a direct shared memory mechanism.

• POSIX assists counting semaphores within the _POSIX_SEMAPHORES option. A counting semaphore permits than one procedure access to a resource at a time.

• Message-Based Communication: in this the shell syntax of pipe is extremely familiar to UNIX users. An illustration appears below.
                       % foo file0| baz > file1

• A parent process employ the pipe () function to make a pipe to talk to a child. This should do so before the child this is created or this won’t have any way to pass a pointer to that pipe to the child.

• The pipe () function give returns an array of file descriptors, therefore the first for the write end and then second for the read end.