03-28-2002
Can you modify the source to the server? If so just have it write its PID to a file somewhere.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi
My script - main.sh, execute program1.sh in background and program2.sh in foreground .
program1.sh holds the process ID of program2.
program1.sh after a while needs to move the process of program2.sh to background.
How? (0 Replies)
Discussion started by: avnerht
0 Replies
2. Shell Programming and Scripting
Hi Guys,
I am facing some weird problem with my shell script. The script shows up a menu and for every ontion internally calls a shell script which start/stop various servers. When I am using '&' while calling the internal shell script so that the server run in the background. For exiting... (1 Reply)
Discussion started by: agoyal
1 Replies
3. Solaris
I ran the Oracle 9i export command from a terminal to export out a big table using "exp andrew/password file=andrew.dmp log=andrew.log"
From the terminal I can see that the export is running as there is some output from the oracle export job. The export job is not complete yet. When i go check... (4 Replies)
Discussion started by: hippo2020
4 Replies
4. Shell Programming and Scripting
Hi,
I have a main script(main.ksh) within which I have called another script(sub.ksh). The sub.ksh script is made to run in the background using '&'. The main.ksh script logs the information in a logfile main_ddmmyy and the sub.ksh script also logs the information in the log file sub_ddmmyy.... (5 Replies)
Discussion started by: chella
5 Replies
5. Shell Programming and Scripting
hey all,
i am working on sun solaris machine and i want to start a process in background using shell script (actually i wanna start tomcat server using shell script). please dont tell me that append a & at last because this is not working in the shell script. i have also used nohup and... (8 Replies)
Discussion started by: dtomar
8 Replies
6. Shell Programming and Scripting
Hey all, I need to launch a script from within 2 other scripts that can run independently of the two parent scripts... Im having a hard time doing this, if anyone knows how please let me know.
More detail.
ScriptA (bash), ScriptB (ksh), ScriptC (bash)
ScriptA, launches ScriptB
ScirptB,... (7 Replies)
Discussion started by: trey85stang
7 Replies
7. UNIX for Dummies Questions & Answers
What I need to learn is how to use a script that launches background processes, and then kills those processes as needed.
The script successfully launches the script. But how do I check to see if the job exists before I kill it?
I know my problem is mostly failure to understand parameter... (4 Replies)
Discussion started by: holocene
4 Replies
8. Shell Programming and Scripting
Hi ,
I am running a backgorund process called hello.sh
./hello &
Now i need to capture the log file as it produces the output .
i am not able to use " >> " nor " tee " to capture the output file / log file .
Please let me know how can i do it ?
Regards,
Deepak Konnur (3 Replies)
Discussion started by: dskonnur
3 Replies
9. Shell Programming and Scripting
Hi,
I am using net::ftp for transferring files now i am trying in the same Linux server as a result ftp is very fast but if the server is other location (remote) then the file transferred will be time consuming.
So i want try putting FTP part as a background process. I am unaware how to do... (5 Replies)
Discussion started by: vanitham
5 Replies
10. Shell Programming and Scripting
Hi,
I have written a menu driven shell script in which as per the choice, I run the another script on background.
For eg:
1. get info
2)process info
3)modify info
All the operations have different scripts which i schedule in background using &.
However I wish to display the error... (0 Replies)
Discussion started by: ashima jain
0 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)