_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
Check Out this Related Man Page
_lwp_kill(2) System Calls _lwp_kill(2)NAME
_lwp_kill - send a signal to a LWP
SYNOPSIS
#include <sys/lwp.h>
#include <signal.h>
int _lwp_kill(lwpid_t target_lwp, int sig);
DESCRIPTION
The _lwp_kill() function sends a signal to the LWP specified by target_lwp. The signal that is to be sent is specified by sig and must be
one from the list given in signal.h(3HEAD). If sig is 0 (the null signal), error checking is performed but no signal is actually sent. This
can be used to check the validity of target_lwp.
The target_lwp must be an LWP within the same process as the calling LWP.
RETURN VALUES
Upon successful completion, 0 is returned. A non-zero value indicates an error.
ERRORS
If any of the following conditions occur, _lwp_kill() fails and returns the corresponding value:
EINVAL The sig argument is not a valid signal number.
ESRCH The target_lwp argument cannot be found in the current process.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|MT-Level |Async-Signal-Safe |
+-----------------------------+-----------------------------+
SEE ALSO kill(2), sigaction(2), sigprocmask(2), signal.h(3HEAD), attributes(5)SunOS 5.10 8 Aug 2001 _lwp_kill(2)
(posted this in the scripting forum as well, but figured it should go here) So, what's going on is this:
For our program, we had to create our own shell, and if the user pressed ctrl-c just at the cmdline, then this signal would be ignored, but if there is a foreground process running, let's... (0 Replies)
Overview:
I'm looking for a way to get usage data for all mount points (UFS,VxFS & NFS) on a Solaris system. I'm starting with `df` but would like to find something that might be more light-weight.
Background:
Using SNMP is not an option in this case, instead I need to use basic built-in... (2 Replies)
My server recently upgraded to LWP 6.0 and I need to turn off SSL Verification. Can someone tell me, step by step, how to do so? The documentation says set PERL_LWP_SSL_VERIFY_HOSTNAME to 0 but I don't know where or how to accomplish this. Thanks!
Below is the error message that I get when... (0 Replies)
Hello,
We had a problem on a Solaris system (SunOS 5.10) that hit LWP limit and caused fork 11 error. Now we need to come up with a script to simulate and reproduce that scenario. What would be a simple and valid way to generate lots of Light Weight Processes?
Thanks,
Jay (1 Reply)