pthread_cond_broadcast(3t) [hpux man page]

pthread_cond_signal(3T) 												   pthread_cond_signal(3T)

NAME

       pthread_cond_signal(), pthread_cond_broadcast() - unblock one or all threads waiting on a condition variable

SYNOPSIS

PARAMETERS

	      cond	Pointer to the condition variable to be signaled or broadcast.

DESCRIPTION

       The  function  is  used to wake-up one of the threads that are waiting for the occurrence of a condition associated with condition variable
       cond.  If there are no threads blocked on cond, this function has no effect.  If more than one thread is blocked on  cond,  the	scheduling
       policy determines which thread is unblocked.  It is possible that more than one thread can be unblocked due to a spurious wakeup.

       The function is used to wake-up all threads that are waiting for the occurrence of a condition associated with the condition variable cond.
       If there are no threads blocked on cond, this function has no effect.  If more than one thread is blocked on cond,  the	scheduling  policy
       determines the order in which threads are unblocked.

       The condition variabled denoted by cond must have been dynamically initialized by a call to or statically initialized with the macro

       An  unblocked  thread  will  reacquire  the  mutex it held when it started the condition wait before returning from or The threads that are
       unblocked contend for the mutex according to their scheduling policy and priority.

       The or functions can be called by a thread whether or not it currently owns the condition variable's  associated  mutex.   For  predictable
       scheduling behavior and to prevent lost wake-ups, the mutex should be held when signaling a condition variable.

   Usage
       When  using  condition variables, there is a boolean predicate associated with each condition wait.  If this predicate is false, the thread
       should do a condition wait.  Spurious wakeups may occur when waiting on a condition variable.  Because the return values from  and  do  not
       imply anything about the value of this predicate, the predicate should always be re-evaluated.

       Applications  using  condition  variables typically acquire a mutex and enter a loop which checks the predicate.  Depending on the value of
       the predicate, the thread either breaks out of the loop or waits on the condition.  On return from the condition wait, the predicate is re-
       evaluated.

RETURN VALUE

       Upon successful completion, and return zero. Otherwise, an error number is returned to indicate the error (the variable is not set).

ERRORS

       For each of the following conditions, if the condition is detected, the and functions return the corresponding error number:

	      [EINVAL]	     cond is not a valid condition variable.

	      [EFAULT]	     cond parameter points to an illegal address.

AUTHOR

       and were derived from the IEEE POSIX P1003.1c standard.

SEE ALSO

       pthread_cond_init(3T), pthread_cond_wait(3T).

STANDARDS CONFORMANCE

								  Pthread Library					   pthread_cond_signal(3T)

Check Out this Related Man Page

pthread_cond_broadcast(3)				     Library Functions Manual					 pthread_cond_broadcast(3)

NAME

       pthread_cond_broadcast - Wakes all threads that are waiting on the specified condition variable.

LIBRARY

       DECthreads POSIX 1003.1c Library (libpthread.so)

SYNOPSIS

       #include <pthread.h>

       int pthread_cond_broadcast(
			pthread_cond_t	*cond);

STANDARDS

       Interfaces documented on this reference page conform to industry standards as follows:

       IEEE Std 1003.1c-1995, POSIX System Application Program Interface

PARAMETERS

       Condition variable upon which the threads (to be awakened) are waiting.

DESCRIPTION

       This  routine unblocks all threads waiting on the specified condition variable cond.  Calling this routine implies that data guarded by the
       associated mutex has changed, so that it might be possible for one or more waiting threads to proceed.	The  threads  that  are  unblocked
       shall contend for the mutex according to their respective scheduling policies (if applicable).

       If  only  one  of  the  threads	waiting  on  a	condition  variable  may  be  able to proceed, but any single thread can proceed, then use
       pthread_cond_signal(3) instead.

       Whether the associated mutex is locked or unlocked, you can still call this  routine.   However,  if  predictable  scheduling  behavior	is
       required, that mutex should then be locked by the thread calling the pthread_cond_broadcast(3) routine.

       If  no threads are waiting on the specified condition variable, this routine takes no action.  The broadcast does not propagate to the next
       condition variable wait.

RETURN VALUES

       If an error condition occurs, this routine returns an integer value indicating the type of error.  Possible return values are  as  follows:
       Successful completion.  The value specified by cond is invalid.

ERRORS

       None

RELATED INFORMATION

       Functions: pthread_cond_destroy(3), pthread_cond_init(3), pthread_cond_signal(3), pthread_cond_timedwait(3), pthread_cond_wait(3)

       Manuals: Guide to DECthreads and Programmer's Guide

       delim off

															 pthread_cond_broadcast(3)

Linux and UNIX Man Pages

pthread_cond_broadcast(3t) [hpux man page]

Check Out this Related Man Page