Executing bash scripts simultaneouslyA script's background process is still alive after closing the terminalscreenrc subshell for every windowRun multiple commands and kill them as one in bashRun commands in a terminal, then let me type more commandsHow do i write a script to run only if another script has run more recently?Synchronous processes in the backgroundRun all scripts in a folder in backgroundHow to troubleshoot failing cron jobIn bash, how can I export/set a global variable from a read funtion inside a script, for use in a second script and a config file later on?Bash run multiple Python scripts with pre-imported modules
Why is there an extra space when I type "ls" in the Desktop directory?
What is the purpose of "me" in "Je me suis trompé dans mon calcul."?
How many characters using PHB rules does it take to be able to have access to any PHB spell at the start of an adventuring day?
Giving a career talk in my old university, how prominently should I tell students my salary?
What are some noteworthy "mic-drop" moments in math?
Are small insurances worth it?
Which situations would cause a company to ground or recall a aircraft series?
Power Strip for Europe
Is it possible that a question has only two answers?
Why does cron require MTA for logging?
Virginia employer terminated employee and wants signing bonus returned
Finitely many repeated replacements
Can't make sense of a paragraph from Lovecraft
Why do we say ‘pairwise disjoint’, rather than ‘disjoint’?
For which categories of spectra is there an explicit description of the fibrant objects via lifting properties?
What would be the most expensive material to an intergalactic society?
Does Christianity allow for believing on someone else's behalf?
Does a difference of tense count as a difference of meaning in a minimal pair?
Is this Paypal Github SDK reference really a dangerous site?
Was it really inappropriate to write a pull request for the company I interviewed with?
What do you call someone who likes to pick fights?
Making a kiddush for a girl that has hard time finding shidduch
What sort of fish is this
What materials can be used to make a humanoid skin warm?
Executing bash scripts simultaneously
A script's background process is still alive after closing the terminalscreenrc subshell for every windowRun multiple commands and kill them as one in bashRun commands in a terminal, then let me type more commandsHow do i write a script to run only if another script has run more recently?Synchronous processes in the backgroundRun all scripts in a folder in backgroundHow to troubleshoot failing cron jobIn bash, how can I export/set a global variable from a read funtion inside a script, for use in a second script and a config file later on?Bash run multiple Python scripts with pre-imported modules
I run several bash scripts in separate terminal windows (tabs). I want to mix them to run in the same window and provide mix outputs. I just need to initiate all scripts independently in the same window.
The common solution is to use &
as
./script1 &
./script2 &
./script3
BUT I don't want to send the scripts to work in the background since I do not have control over them in the terminal. For example, I cannot terminate this script by Ctrl+C
, as the background processes will not be killed by Ctrl+C
.
bash shell-script
add a comment |
I run several bash scripts in separate terminal windows (tabs). I want to mix them to run in the same window and provide mix outputs. I just need to initiate all scripts independently in the same window.
The common solution is to use &
as
./script1 &
./script2 &
./script3
BUT I don't want to send the scripts to work in the background since I do not have control over them in the terminal. For example, I cannot terminate this script by Ctrl+C
, as the background processes will not be killed by Ctrl+C
.
bash shell-script
3
I think you need to readLESS='+/^JOB CONTROL' man bash
. In particular, you can run thejobs
builtin to see a list of current jobs, and can kill them using jobspecs such askill %2
and so forth.
– Wildcard
Mar 1 at 20:39
2
Would something like GNU parallel be useful?
– kemotep
Mar 1 at 20:42
Read up on thepkill
man page: that will make it easier to send an INT signal to the right process.
– glenn jackman
Mar 1 at 20:48
If you run all three and press ctrl+c which one do you want to end?
– Jesse_b
Mar 1 at 21:15
@Jesse_b I want to end all, like it is a single script.
– Googlebot
Mar 1 at 21:46
add a comment |
I run several bash scripts in separate terminal windows (tabs). I want to mix them to run in the same window and provide mix outputs. I just need to initiate all scripts independently in the same window.
The common solution is to use &
as
./script1 &
./script2 &
./script3
BUT I don't want to send the scripts to work in the background since I do not have control over them in the terminal. For example, I cannot terminate this script by Ctrl+C
, as the background processes will not be killed by Ctrl+C
.
bash shell-script
I run several bash scripts in separate terminal windows (tabs). I want to mix them to run in the same window and provide mix outputs. I just need to initiate all scripts independently in the same window.
The common solution is to use &
as
./script1 &
./script2 &
./script3
BUT I don't want to send the scripts to work in the background since I do not have control over them in the terminal. For example, I cannot terminate this script by Ctrl+C
, as the background processes will not be killed by Ctrl+C
.
bash shell-script
bash shell-script
asked Mar 1 at 20:33
GooglebotGooglebot
509623
509623
3
I think you need to readLESS='+/^JOB CONTROL' man bash
. In particular, you can run thejobs
builtin to see a list of current jobs, and can kill them using jobspecs such askill %2
and so forth.
– Wildcard
Mar 1 at 20:39
2
Would something like GNU parallel be useful?
– kemotep
Mar 1 at 20:42
Read up on thepkill
man page: that will make it easier to send an INT signal to the right process.
– glenn jackman
Mar 1 at 20:48
If you run all three and press ctrl+c which one do you want to end?
– Jesse_b
Mar 1 at 21:15
@Jesse_b I want to end all, like it is a single script.
– Googlebot
Mar 1 at 21:46
add a comment |
3
I think you need to readLESS='+/^JOB CONTROL' man bash
. In particular, you can run thejobs
builtin to see a list of current jobs, and can kill them using jobspecs such askill %2
and so forth.
– Wildcard
Mar 1 at 20:39
2
Would something like GNU parallel be useful?
– kemotep
Mar 1 at 20:42
Read up on thepkill
man page: that will make it easier to send an INT signal to the right process.
– glenn jackman
Mar 1 at 20:48
If you run all three and press ctrl+c which one do you want to end?
– Jesse_b
Mar 1 at 21:15
@Jesse_b I want to end all, like it is a single script.
– Googlebot
Mar 1 at 21:46
3
3
I think you need to read
LESS='+/^JOB CONTROL' man bash
. In particular, you can run the jobs
builtin to see a list of current jobs, and can kill them using jobspecs such as kill %2
and so forth.– Wildcard
Mar 1 at 20:39
I think you need to read
LESS='+/^JOB CONTROL' man bash
. In particular, you can run the jobs
builtin to see a list of current jobs, and can kill them using jobspecs such as kill %2
and so forth.– Wildcard
Mar 1 at 20:39
2
2
Would something like GNU parallel be useful?
– kemotep
Mar 1 at 20:42
Would something like GNU parallel be useful?
– kemotep
Mar 1 at 20:42
Read up on the
pkill
man page: that will make it easier to send an INT signal to the right process.– glenn jackman
Mar 1 at 20:48
Read up on the
pkill
man page: that will make it easier to send an INT signal to the right process.– glenn jackman
Mar 1 at 20:48
If you run all three and press ctrl+c which one do you want to end?
– Jesse_b
Mar 1 at 21:15
If you run all three and press ctrl+c which one do you want to end?
– Jesse_b
Mar 1 at 21:15
@Jesse_b I want to end all, like it is a single script.
– Googlebot
Mar 1 at 21:46
@Jesse_b I want to end all, like it is a single script.
– Googlebot
Mar 1 at 21:46
add a comment |
3 Answers
3
active
oldest
votes
You can run your scripts in tmux or screen in almost any number of background processes. Those processes can be accessed in any time you want.
See tmux or GNU screen
add a comment |
You could write a wrapper script around them that sends them all to the background and then traps ctrl+c:
#!/bin/bash
trap ctrl_c INT
scripts=( ./script1.sh ./script2.sh ./script3.sh )
ctrl_c ()
printf 'Found [%i] PIDs runningn' "$#pids[@]"
for pid in "$pids[@]"; do
printf 'Killing PID: %in' "$pid"
kill "$pid"
done
for script in "$scripts[@]"; do
"$script" &
pids+=($!)
done
for pid in "$pids[@]"; do
wait "$pid"
done
So if you press ctrl+c it will kill all the pids that have been previously captured:
$ cat ./script1..3.sh
#!/bin/bash
sleep 30; echo foo
#!/bin/bash
sleep 30; echo bar
#!/bin/bash
sleep 30; echo baz
$ ./script4.sh
^CFound [3] PIDs running
Killing PID: 48971
Killing PID: 48972
Killing PID: 48973
./script4.sh: line 21: 48971 Terminated: 15 "$script"
./script4.sh: line 21: 48972 Terminated: 15 "$script"
./script4.sh: line 21: 48973 Terminated: 15 "$script"
add a comment |
Try:
parallel -j0 --line-buffer ::: ./script1 ./script2 ./script3
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f503871%2fexecuting-bash-scripts-simultaneously%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
You can run your scripts in tmux or screen in almost any number of background processes. Those processes can be accessed in any time you want.
See tmux or GNU screen
add a comment |
You can run your scripts in tmux or screen in almost any number of background processes. Those processes can be accessed in any time you want.
See tmux or GNU screen
add a comment |
You can run your scripts in tmux or screen in almost any number of background processes. Those processes can be accessed in any time you want.
See tmux or GNU screen
You can run your scripts in tmux or screen in almost any number of background processes. Those processes can be accessed in any time you want.
See tmux or GNU screen
answered Mar 1 at 20:41
nestor11nestor11
511
511
add a comment |
add a comment |
You could write a wrapper script around them that sends them all to the background and then traps ctrl+c:
#!/bin/bash
trap ctrl_c INT
scripts=( ./script1.sh ./script2.sh ./script3.sh )
ctrl_c ()
printf 'Found [%i] PIDs runningn' "$#pids[@]"
for pid in "$pids[@]"; do
printf 'Killing PID: %in' "$pid"
kill "$pid"
done
for script in "$scripts[@]"; do
"$script" &
pids+=($!)
done
for pid in "$pids[@]"; do
wait "$pid"
done
So if you press ctrl+c it will kill all the pids that have been previously captured:
$ cat ./script1..3.sh
#!/bin/bash
sleep 30; echo foo
#!/bin/bash
sleep 30; echo bar
#!/bin/bash
sleep 30; echo baz
$ ./script4.sh
^CFound [3] PIDs running
Killing PID: 48971
Killing PID: 48972
Killing PID: 48973
./script4.sh: line 21: 48971 Terminated: 15 "$script"
./script4.sh: line 21: 48972 Terminated: 15 "$script"
./script4.sh: line 21: 48973 Terminated: 15 "$script"
add a comment |
You could write a wrapper script around them that sends them all to the background and then traps ctrl+c:
#!/bin/bash
trap ctrl_c INT
scripts=( ./script1.sh ./script2.sh ./script3.sh )
ctrl_c ()
printf 'Found [%i] PIDs runningn' "$#pids[@]"
for pid in "$pids[@]"; do
printf 'Killing PID: %in' "$pid"
kill "$pid"
done
for script in "$scripts[@]"; do
"$script" &
pids+=($!)
done
for pid in "$pids[@]"; do
wait "$pid"
done
So if you press ctrl+c it will kill all the pids that have been previously captured:
$ cat ./script1..3.sh
#!/bin/bash
sleep 30; echo foo
#!/bin/bash
sleep 30; echo bar
#!/bin/bash
sleep 30; echo baz
$ ./script4.sh
^CFound [3] PIDs running
Killing PID: 48971
Killing PID: 48972
Killing PID: 48973
./script4.sh: line 21: 48971 Terminated: 15 "$script"
./script4.sh: line 21: 48972 Terminated: 15 "$script"
./script4.sh: line 21: 48973 Terminated: 15 "$script"
add a comment |
You could write a wrapper script around them that sends them all to the background and then traps ctrl+c:
#!/bin/bash
trap ctrl_c INT
scripts=( ./script1.sh ./script2.sh ./script3.sh )
ctrl_c ()
printf 'Found [%i] PIDs runningn' "$#pids[@]"
for pid in "$pids[@]"; do
printf 'Killing PID: %in' "$pid"
kill "$pid"
done
for script in "$scripts[@]"; do
"$script" &
pids+=($!)
done
for pid in "$pids[@]"; do
wait "$pid"
done
So if you press ctrl+c it will kill all the pids that have been previously captured:
$ cat ./script1..3.sh
#!/bin/bash
sleep 30; echo foo
#!/bin/bash
sleep 30; echo bar
#!/bin/bash
sleep 30; echo baz
$ ./script4.sh
^CFound [3] PIDs running
Killing PID: 48971
Killing PID: 48972
Killing PID: 48973
./script4.sh: line 21: 48971 Terminated: 15 "$script"
./script4.sh: line 21: 48972 Terminated: 15 "$script"
./script4.sh: line 21: 48973 Terminated: 15 "$script"
You could write a wrapper script around them that sends them all to the background and then traps ctrl+c:
#!/bin/bash
trap ctrl_c INT
scripts=( ./script1.sh ./script2.sh ./script3.sh )
ctrl_c ()
printf 'Found [%i] PIDs runningn' "$#pids[@]"
for pid in "$pids[@]"; do
printf 'Killing PID: %in' "$pid"
kill "$pid"
done
for script in "$scripts[@]"; do
"$script" &
pids+=($!)
done
for pid in "$pids[@]"; do
wait "$pid"
done
So if you press ctrl+c it will kill all the pids that have been previously captured:
$ cat ./script1..3.sh
#!/bin/bash
sleep 30; echo foo
#!/bin/bash
sleep 30; echo bar
#!/bin/bash
sleep 30; echo baz
$ ./script4.sh
^CFound [3] PIDs running
Killing PID: 48971
Killing PID: 48972
Killing PID: 48973
./script4.sh: line 21: 48971 Terminated: 15 "$script"
./script4.sh: line 21: 48972 Terminated: 15 "$script"
./script4.sh: line 21: 48973 Terminated: 15 "$script"
answered Mar 1 at 23:10
Jesse_bJesse_b
13.3k23369
13.3k23369
add a comment |
add a comment |
Try:
parallel -j0 --line-buffer ::: ./script1 ./script2 ./script3
add a comment |
Try:
parallel -j0 --line-buffer ::: ./script1 ./script2 ./script3
add a comment |
Try:
parallel -j0 --line-buffer ::: ./script1 ./script2 ./script3
Try:
parallel -j0 --line-buffer ::: ./script1 ./script2 ./script3
answered 2 hours ago
Ole TangeOle Tange
12.7k1455105
12.7k1455105
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f503871%2fexecuting-bash-scripts-simultaneously%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
-bash, shell-script
3
I think you need to read
LESS='+/^JOB CONTROL' man bash
. In particular, you can run thejobs
builtin to see a list of current jobs, and can kill them using jobspecs such askill %2
and so forth.– Wildcard
Mar 1 at 20:39
2
Would something like GNU parallel be useful?
– kemotep
Mar 1 at 20:42
Read up on the
pkill
man page: that will make it easier to send an INT signal to the right process.– glenn jackman
Mar 1 at 20:48
If you run all three and press ctrl+c which one do you want to end?
– Jesse_b
Mar 1 at 21:15
@Jesse_b I want to end all, like it is a single script.
– Googlebot
Mar 1 at 21:46