cond_signal(3scl)cond_signal(3scl)NAMEcond_signal - Wakes at least one thread that is waiting on the speci‐
fied condition variable.
SCL Threads Library (libthread.so)
cond_t *condp );
Address of the condition variable upon which the threads to be awakened
If there are any threads waiting on the condition variable pointed to
by condp, then this routine will unblock at least one of them (-typi‐
cally only one thread is released).
If no threads are waiting on the specified condition variable, then
this routine takes no action. The signal does not propagate to the next
condition variable wait.
SCL IMPLEMENTATION NOTEScond_signal(3scl) is implemented by calling pthread_cond_signal(3).
cond_signal(3scl) first checks if the specified condition variable is
valid: if it is not, then the condition variable is initialized for
intra-process thread synchronization (type USYNC_THREAD) by calling
pthread_cond_init(3). This action matches the observed behaviour of
If an error condition occurs, this routine returns an integer value
indicating the type of error.
Additional error return information may be written to the SCL error
log. Refer to scl_error_log(4scl) for details.
Possible return values are as follows: Successful completion. Error
from either pthread_cond_init(3) or pthread_cond_signal(3). A message
is written to the SCL errorlog which outlines the error-code mapping.
An internal implementation error occurred. Refer to the SCL errorlog
for additional information.
Note: EFAULT is not returned if condp is an illegal address. An illegal
address generates a SIGSEGV signal, which by default will abort the
process and generate a core dump.
Functions: cond_broadcast(3scl), cond_destroy(3scl), cond_init(3scl),
cond_timedwait(3scl), cond_wait(3scl), pthread_cond_init(3),
pthread_cond_signal(3), scl_intro(3scl), scl_thread_intro(3scl)
Manuals: Solaris Compatibility Libraries User's Guide