02-09-2005
$! is the pid of the most recent process, $$ is the pid of the current process, $PPID is the parent pid. In Korn shell.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hello all,
How do I start a background process and save the process id to a file on my system. For example %wait 5 & will execute and print the process id. I can't figure out how to get it to a file. I've tried: > filename 0>filename 1>filename.
Any assistance is most appreciated.
Thanks,
Jim... (10 Replies)
Discussion started by: jleavitt
10 Replies
2. 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
3. Shell Programming and Scripting
can anybody plz tell me
how can i find the background processes running. (2 Replies)
Discussion started by: Raom
2 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
i gave a copy process in the background( to copy around 100GB) , while in progress, the session got terminated. when i relogged in and checked the destination folder the copying was in progress... how could it happen(copying) when the shell terminates??? :rolleyes: (2 Replies)
Discussion started by: vinod.thayil
2 Replies
6. UNIX for Dummies Questions & Answers
I need to submit a script that will continue to run after logging out and after a reboot or shutdown.
I entered the following: nohup script &
The script continues to run in the background after logging off the system but is killed after a reboot or shutdown. Any help would be greatly... (1 Reply)
Discussion started by: powwm
1 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 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
9. Shell Programming and Scripting
Hi,
I'm gonna launch a process from my 'C' code. I'm gonna launch it a few times. I would like to capture the PID of that process each time I launch. I have to copy the each PIDs into a 'C' variable and I have to kill all of them when I exit from the 'C' code.
My requirement is
int... (3 Replies)
Discussion started by: suryaemlinux
3 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
wait(1) General Commands Manual wait(1)
NAME
wait - await process completion
SYNOPSIS
[pid]
DESCRIPTION
If no argument is specified, waits until all processes (started with of the current shell have completed, and reports on abnormal termina-
tions. If a numeric argument pid is given and is the process ID of a background process, waits until that process has completed. Other-
wise, if pid is not a background process, exits without waiting for any processes to complete.
Because the system call must be executed in the parent process, the shell itself executes without creating a new process (see wait(2)).
Command-Line Arguments
supports the following command line arguments:
The unsigned decimal integer process
ID of a command, whose termination is to wait for.
WARNINGS
Some processes in a 2-or-more-stage pipeline may not be children of the shell, and thus cannot be waited for.
SEE ALSO
csh(1), ksh(1), sh-posix(1), sh(1), wait(2).
STANDARDS CONFORMANCE
wait(1)