01-29-2010
My basic idea for solution would be to spawn initial N workes and save their pids to some table, then sleep 1 and see which of the PIDs are still alive. For those who are not - spawn next worker and save pid in place of the old one. Repeat until job is done.
The problem with counting with pgrep is that you will take in account the processess that may not be related with the script (any other user can run their own gzip, right?).
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I'm trying to install a solaris 9 patch cluster and when I try to use & to run in background it won't allow me to enter in my sudo password so it fails the install and sudo auth. Does Solaris not have screen like linux? If & will work what am I doing wrong?
sudo ./install_cluster -q &
is... (3 Replies)
Discussion started by: kingdbag
3 Replies
2. Shell Programming and Scripting
I have the following sample script to run a script the jobs with the same
priority(in this case field3) in parallel; wait for the jobs to finish
and run the next set of jobs in parallel.When all the lines are read
exit the script.
I have the following script which is doing evrything I want... (1 Reply)
Discussion started by: hyennah
1 Replies
3. Shell Programming and Scripting
i need to execute 5 jobs at a time in background and need to get the exit status of all the jobs i wrote small script below , i'm not sure this is right way to do it.any ideas please help.
$cat run_job.ksh
#!/usr/bin/ksh
####################################
typeset -u SCHEMA_NAME=$1
... (1 Reply)
Discussion started by: GrepMe
1 Replies
4. Shell Programming and Scripting
Hi All,
I have requirement. I am running a job every 30mins. before starting the process, i need to check the process, if the process is still running then i need not trigger the process again, if it is not running then trigger the process again. I am using cron to trigger the shell script. Can... (7 Replies)
Discussion started by: srinivas_paluku
7 Replies
5. Shell Programming and Scripting
Hello,
I am a novice shell script programmer. And facing this problem any help is appreciated.
I m writing a shell script and running few commands in it background as I have to run them simultaneously.
Sample code :
sql_prog &
sql_prog &
sql_prog &
echo "Process Completed"
Here... (2 Replies)
Discussion started by: vineetbhati
2 Replies
6. Shell Programming and Scripting
Hi,
I have on shell script which internally calls more than one scripts which run in background.
These scripts cannot be modified to run in foreground.
eg. myscript.sh -> bulk_launcher.sh -> acq_launcher.sh
-> bulk_loader.sh
I want the calling shell script myscript.sh to wait till the... (7 Replies)
Discussion started by: AB10
7 Replies
7. Shell Programming and Scripting
Hello,
I am running GNU bash, version 3.2.39(1)-release (x86_64-pc-linux-gnu). I have a specific question pertaining to waiting on jobs run in sub-shells, based on the max number of parallel processes I want to allow, and then wait... (1 Reply)
Discussion started by: srao
1 Replies
8. Shell Programming and Scripting
Hi ,
I want to see all the background process that are running in unix box machine...please guide me is there any specific command for that..since I am executing some scripts at background..!!:confused: (1 Reply)
Discussion started by: nks342
1 Replies
9. AIX
Hello,
Please advise use of screen in running jobs in nohup background and how to use this
Best regards,
Vishal (1 Reply)
Discussion started by: Vishal_dba
1 Replies
10. UNIX for Beginners Questions & Answers
Hi,
I have this simple c program that creates duplicate process with fork():
#include <sys/types.h>
main()
{
if (fork() == 0)
while(1);
else
while(1);
}
I tried running it in the background
gcc -o test first.c
test &
And I got this list of running process: (4 Replies)
Discussion started by: uniran
4 Replies
bg(1) General Commands Manual bg(1)
NAME
bg - Runs jobs in the background
SYNOPSIS
bg [job_id...]
Note
The C shell has a built-in version of the bg command. If you are using the C shell, and want to guarantee that you are using the command
described here, you must specify the full path /usr/bin/bg. See the csh(1) reference page for a description of the built-in command.
STANDARDS
Interfaces documented on this reference page conform to industry standards as follows:
bg: XCU5.0
Refer to the standards(5) reference page for more information about industry standards and associated tags.
OPTIONS
None
OPERANDS
Specifies the job to be resumed as a background job. If no job_id operand is given, the most recently suspended job is used. The format of
job_id is described in the Jobs section of the ksh(1) reference page.
DESCRIPTION
If job control is enabled (see the description of set -m in the ksh(1) reference page), the bg utility resumes suspended jobs from the cur-
rent environment by running them as background jobs. If the job specified by job_id is a job already running in the background, the bg
utility has no effect and will exit successfully.
Using bg to place a job into the background causes its process ID to become "known in the current shell execution environment", as if it
had been started as an asynchronous list. See the Jobs section of the ksh(1) reference page.
RESTRICTIONS
If job control is disabled, the bg utility exits with an error and no job is placed in the background. The bg utility does not work as
expected when it is operating in its own utility execution environment because that environment has no suspended jobs.
EXIT STATUS
The following exit values are returned: Successful completion. An error occurred.
ENVIRONMENT VARIABLES
The following environment variables affect the execution of bg: Provides a default value for the internationalization variables that are
unset or null. If LANG is unset or null, the corresponding value from the default locale is used. If any of the internationalization vari-
ables contain an invalid setting, the utility behaves as if none of the variables had been defined. If set to a non-empty string value,
overrides the values of all the other internationalization variables. Determines the locale for the interpretation of sequences of bytes
of text data as characters (for example, single-byte as opposed to multibyte characters in arguments). Determines the locale used to
affect the format and contents of diagnostic messages written to standard error. Determines the location of message catalogues for the
processing of LC_MESSAGES.
SEE ALSO
Commands: csh(1), fg(1), jobs(1), kill(1), ksh(1), Bourne shell sh(1b), POSIX shell sh(1p), wait(1)
Standards: standards(5)
bg(1)