wake up a single LWP waiting on a condition variable
int _lwp_cond_signal(lwp_cond_t *cond);
pointer to condition variable to be signaled
_lwp_cond_signal wakes up a single lightweight process (LWP),
if one exists, waiting on the condition cond.
If more than one LWP is waiting on a condition, the scheduling
policy determines which LWP is awakened.
_lwp_cond_signal has no effect if there are no LWPs waiting on the
The condition variable denoted by cond
must previously have been statically initialized (zero-filled).
_lwp_cond_signal returns zero for success
and an error number for failure, as described below.
If any of the following conditions is detected,
_lwp_cond_signal returns the corresponding value:
Invalid argument specified.
The cond parameter points to an illegal address.
(This error may not be detected; a SIGSEGV signal may be posted to the
faulting LWP if an illegal address is used.)
See the description of how to use condition variables
under USAGE on
Lightweight processes (LWPs) are internal interfaces and are subject
to change. Their use should be avoided.
© 2005 The SCO Group, Inc. All rights reserved.
SCO OpenServer Release 6.0.0 - 01 June 2005