pthread_cond_signal_int_np(3) [osf1 man page]

pthread_cond_signal_int_np(3)				     Library Functions Manual				     pthread_cond_signal_int_np(3)

NAME

       pthread_cond_signal_int_np - Wakes one thread that is waiting on the specified condition variable (called from interrupt level only).

LIBRARY

       DECthreads POSIX 1003.1c Library (libpthread.so)

SYNOPSIS

       #include <pthread.h>

       int pthread_cond_signal_int_np(
			   pthread_cond_t    *cond);

STANDARDS

       None

PARAMETERS

       Condition variable to be signaled.

DESCRIPTION

       This routine wakes one thread waiting on the specified condition variable.  It can only be called from a software interrupt handler routine
       (that is, from a Tru64 UNIX signal handler or OpenVMS AST).  Calling this routine implies that it might be possible for	a  single  waiting
       thread to proceed.

       The  scheduling policies of the waiting threads determine which thread is awakened.  For policies SCHED_FIFO and SCHED_RR, a blocked thread
       is chosen in priority order, using first-in/first-out (FIFO) within priorities.

       This routine does not cause a thread blocked on a condition variable to resume execution immediately. A thread resumes  execution  at  some
       time after the interrupt handler routine returns.

       You  can  call this routine regardless of whether the associated mutex is locked (by some other thread).  Never lock a mutex from an inter-
       rupt handler routine.

									  Note
       This routine allows you to signal a thread from a software interrupt handler.  Do not call this routine from noninterrupt code.	To  signal
       a thread from the normal noninterrupt level, use pthread_cond_signal(3).

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_broadcast(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_signal_int_np(3)

pthread_cond_signal(3C) 				   Standard C Library Functions 				   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);

DESCRIPTION

       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.

RETURN VALUES

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

ERRORS

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

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

ATTRIBUTES

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

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

SEE ALSO

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

SunOS 5.11							    23 Mar 2005 					   pthread_cond_signal(3C)