02-12-2007
get Thread information from process
Hello all
im trying to build small script in tcsh that will monitor some process
that are making some api calles to some server .
first of all im trying to find way to see how many threads each process is using , and else how can i print each
Thread id .
can it be done ? ( using sunOs )
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi,
If we have a process p1 running and then p2 attempts to shutdown p1. Is there a means for p1 to know who has requested him to shutdown
Thanks and regards,
Reji (1 Reply)
Discussion started by: rejise
1 Replies
2. Programming
Hello,
Can some one tell how to read the thread IDs of the current process in Sun Solaris.
Any help will be appreciated.
regards,
Murali (0 Replies)
Discussion started by: hmurali
0 Replies
3. UNIX for Dummies Questions & Answers
What sort of statistical information related to a running process can we retrieve using commands? For example, we can get the process id, memory usage and running time of a process using the commands ps and ipcs . Can we get any more information about a running process?
Please list them. Also... (4 Replies)
Discussion started by: fermisoft
4 Replies
4. Solaris
Hi All:-
1- i am working in unix system that is runnign some script
2- this script put the log file into specific folder
3- the log does not include the start time of the script and the end time
What i need to know what is the duration time for each request
Note:-
I don't any thing... (3 Replies)
Discussion started by: dellsh
3 Replies
5. UNIX for Advanced & Expert Users
Hi folks,
I would like to know how to hook up an xterm to another process.
Here is a high level view of what I am looking for
1. Main program starts
2. It creates an new xterm window
3. It then forks a second process & passes the xterm handle to it
4. The second process uses the second... (4 Replies)
Discussion started by: RipClaw
4 Replies
6. Programming
How do I run a process from a C++ p_thread and obtain its PID? Right now I am doing in a p_thread:
system("ampl method.run");
and into the main function (after running the thread mentioned before):
sleep(5); //Just to be sure that the thread is executing the ampl command
system("ps... (1 Reply)
Discussion started by: riccollado
1 Replies
7. UNIX for Dummies Questions & Answers
i want to know a difference between process and thread,give a program to tell the difference (2 Replies)
Discussion started by: annapurna konga
2 Replies
8. UNIX for Dummies Questions & Answers
Hi,
I want to know a command/program to get thread count for a process id in unix box.
Please help me in this regard. (1 Reply)
Discussion started by: manaac
1 Replies
9. Solaris
Hi Guys
Is it possible to display which process generates the most i/o on my zpool?
With # zpool iostst 3 and iostat i just see the general i/o but not the i/o on the process level.
thx in advance,
Fry (0 Replies)
Discussion started by: fryzh
0 Replies
10. Shell Programming and Scripting
I use top -H -p 1256 to show process 1256, and then press "f" then press "j" to display it is running on which core, is there a better mothed, I want to be automated to get this (1 Reply)
Discussion started by: yanglei_fage
1 Replies
nfsiod(8) System Manager's Manual nfsiod(8)
NAME
nfsiod, biod - The local NFS compatible asynchronous I/O daemon
SYNOPSIS
nfsiod [ numthreads ]
DESCRIPTION
The nfsiod daemon runs on an NFS compatible client machine and spawns several IO threads to service asynchronous I/O requests to its
server. The I/O threads improve performance of both NFS reads and writes. Both try to enlist the aid of an idle I/O thread. If none is
available, the process itself issues the request to the server and waits for the reply.
The optimum number of I/O threads to run depends on many variables, such as how quickly the client will be writing, how many files will be
accessed simultaneously, and the behaviour of the NFS server. For use with a Tru64 UNIX server, 7 is a good number of I/O threads for most
systems.
When reading, if the client believes the process is reading a file sequentially, it requests an I/O thread to read a block ahead of what
the process is currently requesting. If the readahead completes before the process asks for that block, then the subsequent read system
call for that data completes immediately and does not have to wait for the NFS request to complete. Read ahead will be triggered again so
the read may find that next block available as well.
When writing a file, the client takes the process's data, passes the request to an I/O thread and immediately returns to the process. If
the process is writing data faster than the network or server can process, then eventually all the I/O threads become busy and the process
has to handle a NFS write itself. This means the process has to wait until the server finishes the write. For Tru64 UNIX servers, the NFS
block size is 8Kb and UFS tries to cluster I/O 64Kbs at a time. If the client is running with 7 I/O threads, 8 write requests can be in
progress at once. This allows the client and server to write data 64Kbs at a time and is the reason for recommending 7 I/O threads.
Unlike nfsd, each client thread can use either UDP or TCP. However, if TCP mounts are active, the nfsiod process will time out, close idle
TCP connections, and acknowledge any connections closed by the server.
The nfsiod process is also responsible for syncing the access time and modify times for special files and named pipes (fifos). Because I/O
to these files does not go through the NFS server, NFS clients have to directly update the access time and modify time attributes.
The client threads are implemented as kernel threads; they are part of Process ID 0, not the nfsiod process. The ps axml command displays
idle I/O threads under PID 0. Idle threads will be waiting on nfsiod_wait. Therefore, if 7 I/O threads are configured, only 1 nfsiod
process is displayed in the output from the ps command, although 7 client threads are available to handle NFS requests.
FILES
Specifies the command path Specifies the file for logging NFS activity.
RELATED INFORMATION
Commands: nfsd(8), nfsstat(8)
Daemons: async_daemon(2) delim off
nfsiod(8)