_lwp_continue(2) [netbsd man page]

_LWP_SUSPEND(2) 					      BSD System Calls Manual						   _LWP_SUSPEND(2)

NAME

     _lwp_suspend, _lwp_continue -- suspend or continue a light-weight process

LIBRARY

     Standard C Library (libc, -lc)

SYNOPSIS

     #include <lwp.h>

     int
     _lwp_suspend(lwpid_t lwp);

     int
     _lwp_continue(lwpid_t lwp);

DESCRIPTION

     _lwp_suspend() suspends execution of the LWP specified by lwp.  Once an LWP is suspended, subsequent calls to _lwp_suspend() have no effect.
     The only way to resume execution of a suspended LWP is via _lwp_continue().

     _lwp_continue() resumes execution of the LWP specified by lwp.  Once an LWP is resumed, subsequent calls to _lwp_continue() have no effect.

RETURN VALUES

     Upon successful completion, _lwp_suspend() and _lwp_continue() return a value of 0.  Otherwise, an error code is returned to indicate the
     error.

ERRORS

     _lwp_suspend() and _lwp_continue() will fail if:

     [ESRCH]	No LWP can be found in the current process corresponding to that specified by lwp.

     _lwp_suspend() will fail if:

     [EDEADLK]	The LWP specified by lwp is the only LWP in the process.

SEE ALSO

     _lwp_create(2)

HISTORY

     The _lwp_create() system call first appeared in NetBSD 2.0.

BSD
								 January 13, 2003							       BSD

Check Out this Related Man Page

_LWP_KILL(2)						      BSD System Calls Manual						      _LWP_KILL(2)

NAME

     _lwp_kill -- send a signal to a light-weight process

LIBRARY

     Standard C Library (libc, -lc)

SYNOPSIS

     #include <lwp.h>

     int
     _lwp_kill(lwpid_t lwp, int sig);

DESCRIPTION

     _lwp_kill() sends the signal specified by sig to the light-weight process specified by lwp.  If the sig argument is given as 0 (zero),
     _lwp_kill will test for the existence of the target LWP, but will take no further action.

     Job control signals and uncatchable signals can not be directed to a specific LWP: if posted with _lwp_kill, they will affect all LWPs in the
     process.

     Signals will be posted successfully to suspended LWPs, but will not be handled further until the LWP has been continued.

RETURN VALUES

     A 0 value indicates that the call succeeded.  A -1 return value indicates an error occurred and errno is set to indicate the reason.

ERRORS

     [EINVAL]  sig is not a valid signal number.

     [ESRCH]   No LWP can be found in the current process corresponding to that specified by lwp.

SEE ALSO

     _lwp_continue(2), _lwp_suspend(2), kill(2), sigaction(2), signal(7)

HISTORY

     The _lwp_kill() system call first appeared in NetBSD 5.0.

BSD
								 January 20, 2007							       BSD

Linux and UNIX Man Pages

_lwp_continue(2) [netbsd man page]

Check Out this Related Man Page