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













1















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.










share|improve this question

















  • 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







  • 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















1















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.










share|improve this question

















  • 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







  • 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













1












1








1


1






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.










share|improve this question














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






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Mar 1 at 20:33









GooglebotGooglebot

509623




509623







  • 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







  • 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












  • 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







  • 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







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










3 Answers
3






active

oldest

votes


















5














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






share|improve this answer






























    3














    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"





    share|improve this answer






























      0














      Try:



      parallel -j0 --line-buffer ::: ./script1 ./script2 ./script3





      share|improve this answer






















        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
        );



        );













        draft saved

        draft discarded


















        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









        5














        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






        share|improve this answer



























          5














          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






          share|improve this answer

























            5












            5








            5







            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






            share|improve this answer













            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







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Mar 1 at 20:41









            nestor11nestor11

            511




            511























                3














                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"





                share|improve this answer



























                  3














                  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"





                  share|improve this answer

























                    3












                    3








                    3







                    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"





                    share|improve this answer













                    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"






                    share|improve this answer












                    share|improve this answer



                    share|improve this answer










                    answered Mar 1 at 23:10









                    Jesse_bJesse_b

                    13.3k23369




                    13.3k23369





















                        0














                        Try:



                        parallel -j0 --line-buffer ::: ./script1 ./script2 ./script3





                        share|improve this answer



























                          0














                          Try:



                          parallel -j0 --line-buffer ::: ./script1 ./script2 ./script3





                          share|improve this answer

























                            0












                            0








                            0







                            Try:



                            parallel -j0 --line-buffer ::: ./script1 ./script2 ./script3





                            share|improve this answer













                            Try:



                            parallel -j0 --line-buffer ::: ./script1 ./script2 ./script3






                            share|improve this answer












                            share|improve this answer



                            share|improve this answer










                            answered 2 hours ago









                            Ole TangeOle Tange

                            12.7k1455105




                            12.7k1455105



























                                draft saved

                                draft discarded
















































                                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.




                                draft saved


                                draft discarded














                                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





















































                                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

                                Popular posts from this blog

                                What was this official D&D 3.5e Lovecraft-flavored rulebook?What was this set of RPG tools called?As a first-time DM should I let my players play complex character classes and roles?Nymph's Kiss and the RelationshipWhat was the name of this Cleric Prestige Class that shapes metal with its bare hands?Are the 3.5e Dragonlance books third party or official works?What's up with the domain Vile Darkness?What was this 80s book about RPGs?What was the name of this Werewolf band?What book had Rituals to “upgrade” animal companions to keep them viable at higher levels?What was this RPG that had rules for player-owned businesses?

                                Word for a person who has no opinion about whether god existsWord for having a definite opinion while simultaneously withholding judgment?What's the opposite of “newcomer? Is ”veteran" OK?What do you call an “atheist” who might believe in an afterlife?What's a word for someone who wants to voice opinions but not have them challenged?Word for someone who dismisses contrary opinions as irrational?Somone who thinks they are overly special/out of the ordinaryIs there a word, phrase or idiom for “a person who is incapable of thinking about the future”?The belief that a god is human-likeA word for a non-famous person/thing you have heard a lot aboutAdjective for a person who enjoys taking care of their appearance

                                2017 IndyCar Series Contents Series news Teams and drivers Schedule Season summary Footnotes References External links Navigation menu"INDYCAR: Initial 2018 bodywork concepts unveiled"the original"IndyCar confirms switch to Performance Friction brakes in 2017""AJ Foyt Racing will switch to Chevy"the original"Carlos Munoz, Conor Daly will drive for AJ Foyt Racing""Zach Veach's Indy 500 Debut Confirmed with Foyt""No mass exodus from Honda after Ganassi switch""Ex-F1 driver Sato joins Andretti Autosport for 2017 IndyCar season""IndyCar's Ryan Hunter-Reay, sponsor DHL paired through 2020""hhgregg and Andretti Autosport announce partnership for key races in 2016""INDYCAR: Rossi re-signs with Andretti"the original"McLaren Formula 1 - Fernando Alonso to race at Indy 500 with McLaren, Honda and Andretti Autosport""Shank will finally take part in Indy 500 with Harvey, Andretti | MotorSportsTalk""Andretti adds Jack Harvey to Indy 500 field""Ganassi switches to Honda power for 2017""INDYCAR: Chilton returns to Ganassi"the original"IndyCar silly season: Who's going where in 2017?""INDYCAR: Kanaan, NTT Data return to Ganassi"the original"Kimball to remain at Ganassi for 2017""Coyne confirms Bourdais for 2017 IndyCar season""Davison to sub for Bourdais in Indy 500"the original"Gutierrez confirmed for Detroit IndyCar debut""Gutierrez returns with Coyne for rest of 2017 season""Vautier to drive for Coyne at Texas"the original"INDYCAR: Coyne confirms Jones for 2017"the original"Pippa Mann returns to Coyne for Indy 500""Karam, Dreyer & Reinbold teaming up again for Indianapolis 500""Pigot to return to Ed Carpenter Racing""Hildebrand confirmed as full-time Ed Carpenter driver""Veach to replace injured Hildebrand at Barber"the originalNew Team Harding Racing Enters Chaves for 101st Indianapolis 500"Juncos Racing Announces Entry in 101st Running of the Indianapolis 500 :: Juncos Racing""Juncos confirms Pigot for Indy 500""Saavedra confirmed in Juncos' second 500 entry"the original"Lazier confirms Indy 500 run after son's USF2000 debut"the original"Claman DeMelo to race for RLLR at Sonoma"the original"Rahal signs Servia and ace engineer for 2017""IndyCar: Aleshin returns with Schmidt"the original"Aleshin replaced by Saavedra for Toronto""Jack Harvey will pilot SPM No. 7 car at Watkins Glen, Sonoma""Jay Howard confirmed in Tony Stewart's supported SPM Indy entry""INDYCAR: Newgarden to wave the flag at Penske"the original"Pagenaud opts for No. 1 in 2017"the original"Penske confirms Newgarden for 2017""Montoya to stay with Team Penske in 2017""Target leaving IndyCar after 27 seasons with Chip Ganassi""Cavin: IndyCar could see complete driver/team shakeup in 2017""End of the road for KV Racing?""KV Racing confirms closure, equipment sold to Juncos""Juncos confirms IndyCar Series entry"the original"Juncos readies IndyCar program, aims for '17 500"the original"Harding Racing to add Texas, Pocono to schedule"the original"Sato signs with Andretti Autosport for 2017""INDYCAR: Aleshin in Doubt at SPM"the original"Long Beach notebook: JR Hildebrand breaks hand""Hildebrand cleared to return at Phoenix"the original"Bourdais to undergo surgery on multiple fractures""Aleshin loses Schmidt Peterson IndyCar ride""Saavedra in at SPM for Pocono, Gateway"the original"Bourdais to make return at Gateway"the original"The IndyCar Grand Prix no longer is sponsored by Angie's List""2017 IndyCar Series rulebook""2017 Verizon IndyCar Series Official Rulebook"Official websiteeeeee