i am working with embedded system -Dell DCS management sub system. my question is as below:
currently we are using linux kernel 2.6.30 build and we have a kernel logs stored to the /var/log/messages path. now we have to transfer all this logs to the specified SNMP target as a part of SNMP... (4 Replies)
Don't know whether this is right category for this question. I request please consider it and advice correct cotegory if required. Here goes my question.
I want to build a distribution using debian/ubuntu. Currently i'm refering LinuxFromScratch.org, which is asking me a space for around 10gb. I... (3 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)
Hi ,
Currently DELL OMSA SNMP sends data through default udp port 161.I want my custom SNMP MIB also to send data in the same udp port 161.Whether its possible.If yes where to configure .I tried starting my custom MIB in udp port 161,but it throws port already in use.Kindly guide. (1 Reply)
Hi ,
Currently DELL OMSA SNMP sends data through default udp port 161.I want my custom SNMP MIB also to send data in the same udp port 161.Whether its possible.If yes where to configure .I tried starting my custom MIB in udp port 161,but it throws port already in use.Kindly guide. (0 Replies)
_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
