Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: background processing in BASH
Operating Systems Linux background processing in BASH Post 302311684 by jville on Wednesday 29th of April 2009 09:58:46 AM
Old 04-29-2009
here is the o/p after I added set -x

+ ./child1
+ ./child2
+ set +b
+ trap test USR1
+ sleep 1
+ disown 24540
+ wait
in child process 1 child1
in child process 4 child2
in child process 5 child2
in child process 6 child2
+ kill -USR1 24534
++ test
++ jobs -n
++ sed -n '/ Done / s/^\[\([0-9]*\)\].*/\1/p'
+ DONE=
+ '[' -n '' ']'
+ sleep 1
+ disown 25575
+ wait
in child process 2 child1
+ kill -USR1 24534
++ test
++ jobs -n
++ sed -n '/ Done / s/^\[\([0-9]*\)\].*/\1/p'
+ DONE=
+ '[' -n '' ']'
+ sleep 1
+ disown 26616
+ wait
+ kill -USR1 24534
++ test
++ jobs -n
++ sed -n '/ Done / s/^\[\([0-9]*\)\].*/\1/p'
+ DONE=
+ '[' -n '' ']'
+ sleep 1
+ disown 27658
+ wait
in child process 3 child1
+ kill -USR1 24534
++ test
++ jobs -n
++ sed -n '/ Done / s/^\[\([0-9]*\)\].*/\1/p'
+ DONE=
+ '[' -n '' ']'
+ sleep 1
+ disown 28694
+ wait
+ kill -USR1 24534
++ test
++ jobs -n
++ sed -n '/ Done / s/^\[\([0-9]*\)\].*/\1/p'
+ DONE=
+ '[' -n '' ']'
+ sleep 1
+ disown 29744
+ wait
+ kill -USR1 24534
++ test
++ sed -n '/ Done / s/^\[\([0-9]*\)\].*/\1/p'
++ jobs -n
+ DONE=
+ '[' -n '' ']'
+ sleep 1
+ disown 30772
+ wait
+ kill -USR1 24534
++ test
++ jobs -n
++ sed -n '/ Done / s/^\[\([0-9]*\)\].*/\1/p'
+ DONE=
+ '[' -n '' ']'
+ disown 31808
+ wait
+ sleep 1
+ kill -USR1 24534
++ test
++ jobs -n
++ sed -n '/ Done / s/^\[\([0-9]*\)\].*/\1/p'
+ DONE=
+ '[' -n '' ']'
+ sleep 1
+ disown 371
+ wait
+ kill -USR1 24534
++ test
++ jobs -n
++ sed -n '/ Done / s/^\[\([0-9]*\)\].*/\1/p'
+ DONE=
+ '[' -n '' ']'
+ sleep 1
+ disown 1486
+ wait
+ kill -USR1 24534
++ test
++ sed -n '/ Done / s/^\[\([0-9]*\)\].*/\1/p'
++ jobs -n
+ DONE=
+ '[' -n '' ']'
+ sleep 1
+ disown 2516
+ wait

$ + kill -USR1 24534
./p2: line 26: kill: (24534) - No such process
 

10 More Discussions You Might Find Interesting

1. Solaris

Best practice to run bash script in background

nohup /bin/bassh $HOME/scripts/test.sh > $HOME/log/test.log 2>&1 & nohup $HOME/scripts/test.sh > $HOME/log/test.log 2>&1 & Which is the good practice to run a script in background of above two ? does the first one will have any overhead on the system ? our system is SunOS 5.10... (2 Replies)
Discussion started by: mmasals
2 Replies

2. Shell Programming and Scripting

background processing in BASH

I have script 3 scripts 1 parent (p1) and 2 children child1 and child2 I have script 3 scripts 1 parent 2 children child1 child2 In the code below the 2 child processes fire almost Instantaneously in the background, Is that possible to know the status of pass/fail of each process... (12 Replies)
Discussion started by: jville
12 Replies

3. Shell Programming and Scripting

bash tee and background threads

Running centos 2.6, I have a bash script in which I'd like to run a number of background threads in parallel, tee'ing the results of the entire script to one file, while tee'ing the result of each background thread to another. Here's what I'm doing, where the number of csv files control the... (1 Reply)
Discussion started by: heatlamp
1 Replies

4. Programming

Unix Shell background processing

So I made my own unix shell, but i want to make a background process when using the & appended to the end, so far most of the commands seem to work (except cd, but thats another story) right now here is what I have got. Im thinking maybe I shouldn't be using switch and maybe switch it to... (27 Replies)
Discussion started by: Mercfh
27 Replies

5. Shell Programming and Scripting

Background tasks in a loop (bash)

I am trying to use a loop to start tasks 0-3, running 0,1,2 in the background with &. FOLDSET=( 0 1 2 3 ) for FOLDSET in ${FOLDSET} do if ; then BACKGRD="&" else BACKGRD="" fi # start task $FOLDSET task1 -nogui -ni -p $PROJ \ epochs=$EPOS ... (3 Replies)
Discussion started by: LMHmedchem
3 Replies

6. Shell Programming and Scripting

BASH - Handling background processes - distributed processing

NOTE: I am using BASH and Solaris 10 for this. Currently in the process of building a script that has a main "watcher" daemon that reads a configuration file and starts background processes based on it's global configuration. It is basically an infinite loop of configuration reading. Some of the... (4 Replies)
Discussion started by: dcarrion87
4 Replies

7. Shell Programming and Scripting

Suppress a background message in Bash

I'm having trouble with part of this bash script in Linux where I respawn a new instance of script and kill the old one to prevent forking (Yes, I know 'exec' will not fork but this needs to be interactive) When the old instance is kill it pops up "Terminated!" in the middle of the new instance... (7 Replies)
Discussion started by: Azrael
7 Replies

8. Shell Programming and Scripting

Parallel processing in bash?

Hi Say I am interested in processing a big data set over shell, and each process individually takes a long time, but many such processes can be pipe-lined, is there a way to do this automatically or efficiently in shell? For example consider pinging a list addresses upto 5 times each. Of... (5 Replies)
Discussion started by: jamie_123
5 Replies

9. Shell Programming and Scripting

Plink (processing multiple commands) using Bash

I'm completely brand new to bash scripting (migrating from Windows batch file scripting). I'm currently trying to write a bash script that will automatically reset "error-disabled" Cisco switch ports. Please forgive the very crude and inefficient script I have so far (shown below). It is... (10 Replies)
Discussion started by: MKANET
10 Replies

10. Shell Programming and Scripting

[Help] Bash script that runs in the background and checks for mails...

Hello! I have got a homework. The bash script runs in the background and checks the user's mailbox and when the user gets a new mail a popup window appears with some text and information about the sender (from who and when).I have no idea how to start, any help would be appreciated! Thank you:) (1 Reply)
Discussion started by: capo2ndfret
1 Replies

LEARN ABOUT POSIX

queuedefs

queuedefs(4)                                                       File Formats                                                       queuedefs(4)

NAME

       queuedefs - queue description file for at, batch, and cron

SYNOPSIS

       /etc/cron.d/queuedefs

DESCRIPTION

       The queuedefs file describes the characteristics of the queues managed by cron(1M). Each non-comment line in this file describes one queue.
       The format of the lines are as follows:

              q.[njobj][nicen][nwaitw]

       The fields in this line are:

       q        The name of the queue. a is the default queue for jobs started by at(1); b is the default queue for jobs  started  by  batch  (see
                at(1)); c is the default queue for jobs run from a crontab(1) file.

       njob     The  maximum  number of jobs that can be run simultaneously in that queue; if more than njob jobs are ready to run, only the first
                njob jobs will be run, and the others will be run as jobs that are currently running terminate.  The default value is  100.

       nice     The nice(1) value to give to all jobs in that queue that are not run with a user ID of super-user.  The default value is 2.

       nwait    The number of seconds to wait before rescheduling a job that was deferred because more than njob jobs were running in  that  job's
                queue, or because the system-wide limit of jobs executing has been reached.  The default value is 60.

       Lines beginning with # are comments, and are ignored.

EXAMPLES

       Example 1: A sample file.

       #
       #
       a.4j1n
       b.2j2n90w

       This  file  specifies that the a queue, for at jobs, can have up to 4 jobs running simultaneously; those jobs will be run with a nice value
       of 1.  As no nwait value was given, if a job cannot be run because too many other jobs are running cron will wait 60 seconds before  trying
       again to run it.

       The  b  queue, for batch(1) jobs, can have up to 2 jobs running simultaneously; those jobs will be run with a nice(1) value of 2.  If a job
       cannot be run because too many other jobs are running, cron(1M) will wait 90 seconds before trying again to run it. All  other  queues  can
       have up to 100 jobs running simultaneously; they will be run with a nice value of 2, and if a job cannot be run because too many other jobs
       are running cron will wait 60 seconds before trying again to run it.

FILES

       /etc/cron.d/queuedefs           queue description file for  at, batch, and  cron.

SEE ALSO

       at(1), crontab(1), nice(1), cron(1M)

SunOS 5.10                                                          1 Mar 1994                                                        queuedefs(4)
All times are GMT -4. The time now is 09:15 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy