In ksh at least this is easy. First when you background a job, save the value of $! which will be the pid of the background job. The background job will eventally finish and become a zombie. It will stay a zomblie until the parent waits for it and retrieves the exit code. In ksh, this is done with the "wait" command. The exit code of the wait command will be the exit code of the process that was waited for. This sounds complex but try this script:
However, in your sample, I don't see why you bothered to background the job, since the next step is to ask if it worked. Why not just leave it in the foreground? Well, maybe it was just an over-simplified example much like my own sample code.
hi there,
here's what i need in my korn-shell:
... begin korn-shell script
... nohup process_A.ksh ; nohup process_B.ksh &
... "other stuff"
... end lorn-shell script
in plain english i want process A and process B to run in the background so that the script can continue doing... (6 Replies)
Hey guys,
I am writing a very simple dummy shell in C++ and I am having trouble getting a process to run in the background. First of all, the shell has to recognize when I input a "&" at the end of the command, then it has to stick it in the background of the shell.
I understand that if I want... (6 Replies)
Hi!
First of all, let me warn you I'm quite new to the world of LINUX and Operating Systems understanding, so that's why I pose these newbie and stupid qustions...
Anyway, I'm trying to build my own simple shell in C and I'm getting some problems in implementing the background process ('&')... (10 Replies)
I have installed oracle 10g on suse sles9. I do not see oracle background processes.
ps -ef|grep ora_ gives me environment variables junk.
ps -ef|grep smon does not show anything however database is up and running.
Any idea how to tweak that? (1 Reply)
I've got a bit of code I'm trying to work on...
What i want to happen is ... at all times have four parallel mysql dump and imports running.
I found the follow code snippet on the forum and modified it to work
by starting four concurrent processes but it waits until all four are done before... (7 Replies)
Hi,
Inorder to improve the performance, I am trying to execute my command as a background process..
For eg: To zip large numbers of files present in a directory instead of using a single process, i do follow the below method:
gunzip -c > / &... (3 Replies)
Hi,
I need to establish a procedure that will start an application in background each time my remote Solaris server is (re)started. This would be a kind of daemon. I am no sysadmin expert, so I am looking for pointers.
How should I proceed? What are the main steps?
Thanks,
JVerstry (9 Replies)
Ok guys so I have my first dummy shell almost done except for one tiny part: I do not know how to run a process in the background, from the code!
I already know how to do that in a normal shell:
$ program &
However, no clue when it comes to how to program that thing. :eek:
A very... (2 Replies)
Hi,
I have a schell script parent.ksh from which I am calling three background processes a.ksh,b.ksh and c.ksh. Once these three processes completes the next step in parent.ksh should execute. How to achieve this?
Please help me....
Thanks... (1 Reply)
How do I list the process in a Unix based system which are running in background?
The following are options that I'm aware of, but they may not be appropiate.
a. using ps -ef , and getting records of processes for which STATUS='S'(uninterruptible sleep)
b. using jobs -l, and filtering... (5 Replies)
Discussion started by: kumarjt
5 Replies
LEARN ABOUT NETBSD
wait
WAIT(1) BSD General Commands Manual WAIT(1)NAME
wait -- await process completion
SYNOPSIS
wait [pid]
DESCRIPTION
If invoked with no arguments, the wait utility waits until all existing child processes in the background have terminated.
Available operands:
pid If a pid operand is specified, and it is the process ID of a background child process that still exists, the wait utility waits until
that process has completed and consumes its status information, without consuming the status information of any other process.
If a pid operand is specified that is not the process ID of a child background process that still exists, wait exits without waiting
for any processes to complete.
The wait utility exits with one of the following values:
0 The wait utility was invoked with no operands and all of the existing background child processes have terminated, or the process
specified by the pid operand exited normally with 0 as its exit status.
>0 The specified process did not exist and its exit status information was not available, or the specified process existed or its exit
status information was available, and it terminated with a non-zero exit status.
If the specified process terminated abnormally due to the receipt of a signal, the exit status information of wait contains that termination
status as well.
STANDARDS
The wait command is expected to be IEEE Std 1003.2 (``POSIX.2'') compatible.
BSD June 5, 1993 BSD