pthread_cond_broadcast(3c) [sunos man page]

pthread_cond_signal(3C) 												   pthread_cond_signal(3C)

NAME

       pthread_cond_signal, pthread_cond_broadcast - signal or broadcast a condition

SYNOPSIS

       cc -mt [ flag... ] file... -lpthread [ library... ]
       #include <pthread.h>

       int pthread_cond_signal(pthread_cond_t *cond);

       int pthread_cond_broadcast(pthread_cond_t *cond);

       These two functions are used to unblock threads blocked on a condition variable.

       The  pthread_cond_signal()  call  unblocks  at  least  one of the threads that are blocked on the specified condition variable cond (if any
       threads are blocked on cond).

       The pthread_cond_broadcast() call unblocks all threads currently blocked on the specified condition variable cond.

       If more than one thread is blocked on a condition variable, the scheduling policy determines the order in which threads are unblocked. When
       each  thread  unblocked	as a result of a pthread_cond_signal() or pthread_cond_broadcast() returns from its call to pthread_cond_wait() or
       pthread_cond_timedwait(), the thread owns the mutex with which it called pthread_cond_wait()  or  pthread_cond_timedwait().  The  thread(s)
       that   are   unblocked  contend	for  the  mutex  according  to	the  scheduling  policy  (if  applicable),  and  as  if  each  had  called
       pthread_mutex_lock().

       The pthread_cond_signal() or pthread_cond_broadcast() functions may be called by a thread whether or not it currently owns the  mutex  that
       threads calling pthread_cond_wait() or pthread_cond_timedwait() have associated with the condition variable during their waits; however, if
       predictable scheduling behavior is required, then that mutex is locked by the thread calling pthread_cond_signal()  or  pthread_cond_broad-
       cast().

       The pthread_cond_signal() and pthread_cond_broadcast() functions have no effect if there are no threads currently blocked on cond.

       If  successful, the pthread_cond_signal() and pthread_cond_broadcast() functions return	0. Otherwise, an error number is returned to indi-
       cate the error.

       The  pthread_cond_signal() and pthread_cond_broadcast() function may fail if:

       EINVAL	       The value cond does not refer to an initialized condition variable.

       See attributes(5) for descriptions of the following attributes:

       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Interface Stability	     |Standard			   |
       +-----------------------------+-----------------------------+
       |MT-Level		     |MT-Safe			   |
       +-----------------------------+-----------------------------+

       pthread_cond_init(3C), pthread_cond_wait(3C), pthread_cond_timedwait(3C), attributes(5), condition(5), standards(5)

								    23 Mar 2005 					   pthread_cond_signal(3C)

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(3c) [sunos man page]

Check Out this Related Man Page