Print this page
12309 errors in section 9e of the manual
@@ -60,17 +60,17 @@
customized at initialization.
The cond_init() function initializes the condition variable pointed to
by cvp. A condition variable can have several different types of
- behavior, specified by type. No current type uses arg although a
- future type may specify additional behavior parameters with arg. The
- type argument c take one of the following values:
+ behavior, specified by type. No current type uses arg although a future
+ type may specify additional behavior parameters with arg. The type
+ argument c take one of the following values:
USYNC_THREAD
- The condition variable can synchronize threads only
- in this process. This is the default.
+ The condition variable can synchronize threads only in
+ this process. This is the default.
USYNC_PROCESS
The condition variable can synchronize threads in this
process and other processes. Only one process should
@@ -128,12 +128,12 @@
The cond_wait() function atomically releases the mutex pointed to by mp
and causes the calling thread to block on the condition variable
pointed to by cvp. The blocked thread may be awakened by cond_signal(),
- cond_broadcast(), or when interrupted by delivery of a UNIX signal or
- a fork().
+ cond_broadcast(), or when interrupted by delivery of a UNIX signal or a
+ fork().
The cond_wait(), cond_timedwait(), and cond_reltimedwait() functions
always return with the mutex locked and owned by the calling thread
even when returning an error, except when the mutex has the LOCK_ROBUST
@@ -232,11 +232,11 @@
EXAMPLES
Example 1 Use cond_wait() in a loop to test some condition.
- The cond_wait() functin is normally used in a loop testing some
+ The cond_wait() function is normally used in a loop testing some
condition, as follows:
(void) mutex_lock(mp);
while (cond == FALSE) {
@@ -329,6 +329,6 @@
either cond_timedwait() or cond_reltimedwait() returns because of a
timeout, it returns the error value ETIME.
- June 5, 2007 COND_INIT(3C)
+ February 15, 2020 COND_INIT(3C)