83        +---------------+-----------------+
  84        |ATTRIBUTE TYPE | ATTRIBUTE VALUE |
  85        +---------------+-----------------+
  86        |MT-Level       | MT-Safe         |
  87        +---------------+-----------------+
  88 
  89 SEE ALSO
  90        fork(2), mmap(2), setitimer(2), shmop(2), cond_broadcast(3C),
  91        cond_destroy(3C), cond_init(3C), cond_signal(3C), cond_timedwait(3C),
  92        cond_wait(3C), pthread_cond_broadcast(3C), pthread_cond_destroy(3C),
  93        pthread_cond_init(3C), pthread_cond_signal(3C),
  94        pthread_cond_timedwait(3C), pthread_cond_wait(3C),
  95        pthread_condattr_init(3C), signal(3C), attributes(5), mutex(5),
  96        standards(5)
  97 
  98 NOTES
  99        If more than one thread is blocked on a condition variable, the order
 100        in which threads are unblocked is determined by the scheduling policy.
 101 
 102 
 103        USYNC_THREAD does not support multiple mapplings to the same logical
 104        synch object. If you need to mmap() a synch object to different
 105        locations within the same address space, then the synch object should
 106        be initialized as a shared object USYNC_PROCESS for Solaris, and
 107        PTHREAD_PROCESS_PRIVATE for POSIX.
 108 
 109 
 110 
 111                                  July 20, 1998                    CONDITION(5)

  83        +---------------+-----------------+
  84        |ATTRIBUTE TYPE | ATTRIBUTE VALUE |
  85        +---------------+-----------------+
  86        |MT-Level       | MT-Safe         |
  87        +---------------+-----------------+
  88 
  89 SEE ALSO
  90        fork(2), mmap(2), setitimer(2), shmop(2), cond_broadcast(3C),
  91        cond_destroy(3C), cond_init(3C), cond_signal(3C), cond_timedwait(3C),
  92        cond_wait(3C), pthread_cond_broadcast(3C), pthread_cond_destroy(3C),
  93        pthread_cond_init(3C), pthread_cond_signal(3C),
  94        pthread_cond_timedwait(3C), pthread_cond_wait(3C),
  95        pthread_condattr_init(3C), signal(3C), attributes(5), mutex(5),
  96        standards(5)
  97 
  98 NOTES
  99        If more than one thread is blocked on a condition variable, the order
 100        in which threads are unblocked is determined by the scheduling policy.
 101 
 102 
 103        USYNC_THREAD does not support multiple mappings to the same logical
 104        synch object. If you need to mmap() a synch object to different
 105        locations within the same address space, then the synch object should
 106        be initialized as a shared object USYNC_PROCESS for Solaris, and
 107        PTHREAD_PROCESS_PRIVATE for POSIX.
 108 
 109 
 110 
 111                                  May 16, 2020                     CONDITION(5)