Skip Navigation Links | |
Exit Print View | |
Programming Interfaces Guide Oracle Solaris 11 Express 11/10 |
2. Remote Shared Memory API for Solaris Clusters
3. Session Description Protocol API
POSIX Interprocess Communication
Permissions for Messages, Semaphores, and Shared Memory
IPC Interfaces, Key Arguments, and Creation Flags
Sending and Receiving Messages
Accessing a Shared Memory Segment
Controlling a Shared Memory Segment
Attaching and Detaching a Shared Memory Segment
9. Programming With XTI and TLI
11. Transport Selection and Name-to-Address Mapping
12. Real-time Programming and Administration
Named pipes function much like pipes, but are created as named entities in a file system. This enables the pipe to be opened by all processes with no requirement that they be related by forking. A named pipe is created by a call to mknod(2). Any process with appropriate permission can then read or write to a named pipe.
In the open(2) call, the process opening the pipe blocks until another process also opens the pipe.
To open a named pipe without blocking, the open(2) call joins the O_NDELAY mask (found in sys/fcntl.h) with the selected file mode mask using the Boolean or operation on the call to open(2). If no other process is connected to the pipe when open(2) is called, -1 is returned with errno set to EWOULDBLOCK.