02-17-2008
From your description, it's difficult to know if U program in C, XWindow, or scripting in Perl, ksh or dtksh... but maybe the easiest way is to use named pipes.
Simply creates your named pipes and read/write to them from any process or thread...
For example, main process creates 5 threads, each thread create his named pipe and write data to his named pipe, main process then creates 5 xterm process reading and printing each named pipes...
Also, if the data is not volatile, threads can write data to regular files and xterm processes could read them continuously like 'tail -f'...
We are limited just by our imagination... depending on the task to do, U can use shared memory, memory mapped files, message queues, database, indexed files, etc...
10 More Discussions You Might Find Interesting
1. 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
2. Shell Programming and Scripting
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 ) (2 Replies)
Discussion started by: umen
2 Replies
3. Shell Programming and Scripting
I have no idea how to do this:
Let's say the user opens an "xclock &" in one of my scripts and I don't want him to be able to re-open one with the script. How could I test that? Possibly with a message saying that "The <xclock(or w/e other process like xcalc)> is already running in the... (3 Replies)
Discussion started by: Yakuzan
3 Replies
4. UNIX for Advanced & Expert Users
Hi,
I was logged in on a server, by ssh, with a vim open, when the battery of my laptop got empty.
When I return to the server by ssh, I can see my previous ssh session still open, and the vim process running (ttyp0). Is there a way to attach that vim to my new session (ttyp4)?
Here's part... (2 Replies)
Discussion started by: raphinou
2 Replies
5. 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
6. 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
7. 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
8. Programming
Hey everyone,
I have a process that is crashing, and I'd like to have some way to see where it crashes. Is this possible? (2 Replies)
Discussion started by: ctote
2 Replies
9. 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
10. UNIX for Beginners Questions & Answers
Hi Team,
is there any way, I can start any process for e.g. run a shell script (infinite loop) and attach it to port 2222?
I am trying to create a scenario where an application will start running at port 2222 and I will telnet the same to confirm, application port is listening.
So,... (1 Reply)
Discussion started by: vivekpandit7
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)