12-19-2002
We are working on SunOS Rel 5.8.Infact I have worked on the method - counting the number of subdirectories in the /proc/[pid]/lwp by using the following algorithm :
.......
/* After I have found the pid of the required process */
sprintf ( Dir , "/proc/%d/lwp" , pid ) ;
if ( ! chdir ( Dir ) ) {
Counter = 0 ;
if ((dp = opendir ( Dir ))!= NULL) {
while((dirp=readdir(dp))!=NULL)
if(dirp->d_name[0]!='.') Counter ++ ;
}
}
.......
I get the right count of subdirectories in the variable Counter. But the threads created in the program does not matches in number to subdirectories in /proc/[pid]/lwp. For example in an application I have created two thread by using pthread_create but number of subdirectories created in lwp directory for that process is five.I am not able to figure it as to why this difference exists.
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
NPTL(7) Linux Programmer's Manual NPTL(7)
NAME
nptl - Native POSIX Threads Library
DESCRIPTION
NPTL (Native POSIX Threads Library) is the GNU C library POSIX threads implementation that is used on modern Linux systems.
NPTL and signals
NPTL makes internal use of the first two real-time signals (signal numbers 32 and 33). One of these signals is used to support thread can-
cellation and POSIX timers (see timer_create(2)); the other is used as part of a mechanism that ensures all threads in a process always
have the same UIDs and GIDs, as required by POSIX. These signals cannot be used in applications.
To prevent accidental use of these signals in applications, which might interfere with the operation of the NPTL implementation, various
glibc library functions and system call wrapper functions attempt to hide these signals from applications, as follows:
* SIGRTMIN is defined with the value 34 (rather than 32).
* The sigwaitinfo(2), sigtimedwait(2), and sigwait(3) interfaces silently ignore requests to wait for these two signals if they are speci-
fied in the signal set argument of these calls.
* The sigprocmask(2) and pthread_sigmask(3) interfaces silently ignore attempts to block these two signals.
* The sigaction(2), pthread_kill(3), and pthread_sigqueue(3) interfaces fail with the error EINVAL (indicating an invalid signal number)
if these signals are specified.
* sigfillset(3) does not include these two signals when it creates a full signal set.
NPTL and process credential changes
At the Linux kernel level, credentials (user and group IDs) are a per-thread attribute. However, POSIX requires that all of the POSIX
threads in a process have the same credentials. To accommodate this requirement, the NPTL implementation wraps all of the system calls
that change process credentials with functions that, in addition to invoking the underlying system call, arrange for all other threads in
the process to also change their credentials.
The implementation of each of these system calls involves the use of a real-time signal that is sent (using tgkill(2)) to each of the other
threads that must change its credentials. Before sending these signals, the thread that is changing credentials saves the new creden-
tial(s) and records the system call being employed in a global buffer. A signal handler in the receiving thread(s) fetches this informa-
tion and then uses the same system call to change its credentials.
Wrapper functions employing this technique are provided for setgid(2), setuid(2), setegid(2), seteuid(2), setregid(2), setreuid(2), setres-
gid(2), setresuid(2), and setgroups(2).
CONFORMING TO
For details of the conformance of NPTL to the POSIX standard, see pthreads(7).
NOTES
POSIX says that any thread in any process with access to the memory containing a process-shared (PTHREAD_PROCESS_SHARED) mutex can operate
on that mutex. However, on 64-bit x86 systems, the mutex definition for x86-64 is incompatible with the mutex definition for i386, meaning
that 32-bit and 64-bit binaries can't share mutexes on x86-64 systems.
SEE ALSO
credentials(7), pthreads(7), signal(7), standards(7)
Linux 2015-08-08 NPTL(7)