Interprocess communication

Interprocess communication

SCO OpenServer provides several mechanisms that allow processes to exchange data and synchronize execution. The simpler of these mechanisms are pipes, named pipes, and signals. These are limited, however, in what they can do. For instance,

SCO OpenServer also provides an InterProcess Communication (IPC) package that supports three, more versatile types of interprocess communication. For example,

When implemented as a unit, these three mechanisms share common properties such as

This section describes the system calls for each of these three forms of IPC.

This information is for programmers who write multiprocess applications. These programmers should have a general understanding of what semaphores are and how they are used.

Information from other sources would also be helpful. See ipcs(ADM) and ipcrm(ADM), as well as the following manual pages:

intro(S) aclipc(S)

msgget(S) msgctl(S) msgop(S)
semget(S) semctl(S) semop(S)
shmget(S) shmctl(S) shmop(S)

Included in this section are several example programs that show the use of these IPC system calls. Since there are many ways to accomplish the same task or requirement, keep in mind that the example programs were written for clarity and not for program efficiency. Usually, system calls are embedded within a larger user-written program that makes use of a particular function provided by the calls.

Next topic: Messages

© 2005 The SCO Group, Inc. All rights reserved.
SCO OpenServer Release 6.0.0 -- 02 June 2005