12-26-2002
Quote:
Originally posted by S.P.Prasad
When the kernel realizes that all of a process's LWPs are blocked at the kernel level, it drops a SIGWAITING on the process. Upon receipt of the signal, the user-level threads package decides whether or not to create a new LWP, on the basis of the number of runnable threads.
That is interesting. I've been looking for some info on SIGWAITING. Do you have any info on SIGLWP as well?
Hmmm, it's not obvious to me how the SIGWAITING signal handler is run if all the lwp's are blocked. Does the thread library keep one lwp to itself? That would explain the 3 lwp's created as a default. One for the library itself and two for the user.
10 More Discussions You Might Find Interesting
1. HP-UX
hi,all:
how to see the threads count of a process in hp unix?
thanks (2 Replies)
Discussion started by: bugbugbug
2 Replies
2. Linux
Hi
Anybody knows max. no. of threads handled by a process in linux. Please reply
Thanks in advnce :confused: (0 Replies)
Discussion started by: Agnello
0 Replies
3. UNIX for Advanced & Expert Users
Hi all,
How can I get the list of all Threads and the Total count of threads under a particular process ?
Do suggest !!
Awaiting for the replies !!
Thanks
Varun:b: (2 Replies)
Discussion started by: varungupta
2 Replies
4. HP-UX
Hi,
I have a process which creates pthreads to generate some reports. After creating the reports these threads return null. But after 1024 threads, the process is not able to create any threads further.,and at max 5 threads are existing simultaneously and are returning the control back after... (2 Replies)
Discussion started by: Krsh
2 Replies
5. UNIX for Advanced & Expert Users
What are the maximum number of threads possible per Process? Is it OS dependent? (1 Reply)
Discussion started by: digdarshan
1 Replies
6. Solaris
Is there any command to find
1) the number of threads running
2) kernel boot mode
in solaris box (2 Replies)
Discussion started by: vickylife
2 Replies
7. Shell Programming and Scripting
Hi experts a have a very large file and I need to add two columns: the first one numbering the incidence of records and the another with the total count
The input file:
21 2341 A
21 2341 A
21 2341 A
21 2341 C
21 2341 C
21 2341 C
21 2341 C
21 4567 A
21 4567 A
21 4567 C
... (6 Replies)
Discussion started by: juelillo
6 Replies
8. AIX
Hello,
On Linux, I can use 'ps -efL | grep process_name' to list all threads that belong to a running process. -L has a different meaning on AIX and I could not find an equivalent flag in the man pages.
Does anyone know of a way to dump the threads under a running process?
Thanks,... (2 Replies)
Discussion started by: makodarear
2 Replies
9. SuSE
I have this error message from the logs of Zimbra email running on SUSE 11.2
Is the thread maximum of 20 an operating system parameter, or is it part of the application code, or part of the java run time?
Part two, how would I increase that number? (3 Replies)
Discussion started by: jgt
3 Replies
10. HP-UX
Hi All,
When i was trying to get total number of threads per java process using this command ps -o NLWP PID, I'm not getting any output. Could someone help me in this issue.
Thanks,
GMar (1 Reply)
Discussion started by: mgangumolu
1 Replies
LEARN ABOUT NETBSD
_lwp_kill
_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