Run Application using Command without blocking Terminal












0















I have made some command (at /usr/bin) to Run Application like Matlab, Weka etc in Ubuntu 18.04 LTS. While using Matlab command, it holds the Terminal until I close Matlab or Terminal (if I close Terminal, Matlab also closed). How can I avoid this problem, that means Matlab command will not hold terminal while working? Thank You.



The Following Format has worked before but suddenly not working.



#!/bin/bash

setsid /usr/local/MATLAB/R2018a/bin/matlab </dev/null >/dev/null 2>&1 & disown


Now Matlab just open the logo but no further work going on....










share|improve this question







New contributor




Shaikat Saha is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





















  • Has there been any recent update for Matlab that you recall ?

    – Sergiy Kolodyazhnyy
    1 hour ago
















0















I have made some command (at /usr/bin) to Run Application like Matlab, Weka etc in Ubuntu 18.04 LTS. While using Matlab command, it holds the Terminal until I close Matlab or Terminal (if I close Terminal, Matlab also closed). How can I avoid this problem, that means Matlab command will not hold terminal while working? Thank You.



The Following Format has worked before but suddenly not working.



#!/bin/bash

setsid /usr/local/MATLAB/R2018a/bin/matlab </dev/null >/dev/null 2>&1 & disown


Now Matlab just open the logo but no further work going on....










share|improve this question







New contributor




Shaikat Saha is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





















  • Has there been any recent update for Matlab that you recall ?

    – Sergiy Kolodyazhnyy
    1 hour ago














0












0








0








I have made some command (at /usr/bin) to Run Application like Matlab, Weka etc in Ubuntu 18.04 LTS. While using Matlab command, it holds the Terminal until I close Matlab or Terminal (if I close Terminal, Matlab also closed). How can I avoid this problem, that means Matlab command will not hold terminal while working? Thank You.



The Following Format has worked before but suddenly not working.



#!/bin/bash

setsid /usr/local/MATLAB/R2018a/bin/matlab </dev/null >/dev/null 2>&1 & disown


Now Matlab just open the logo but no further work going on....










share|improve this question







New contributor




Shaikat Saha is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












I have made some command (at /usr/bin) to Run Application like Matlab, Weka etc in Ubuntu 18.04 LTS. While using Matlab command, it holds the Terminal until I close Matlab or Terminal (if I close Terminal, Matlab also closed). How can I avoid this problem, that means Matlab command will not hold terminal while working? Thank You.



The Following Format has worked before but suddenly not working.



#!/bin/bash

setsid /usr/local/MATLAB/R2018a/bin/matlab </dev/null >/dev/null 2>&1 & disown


Now Matlab just open the logo but no further work going on....







matlab






share|improve this question







New contributor




Shaikat Saha is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question







New contributor




Shaikat Saha is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question






New contributor




Shaikat Saha is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked 3 hours ago









Shaikat SahaShaikat Saha

82




82




New contributor




Shaikat Saha is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





Shaikat Saha is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






Shaikat Saha is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.













  • Has there been any recent update for Matlab that you recall ?

    – Sergiy Kolodyazhnyy
    1 hour ago



















  • Has there been any recent update for Matlab that you recall ?

    – Sergiy Kolodyazhnyy
    1 hour ago

















Has there been any recent update for Matlab that you recall ?

– Sergiy Kolodyazhnyy
1 hour ago





Has there been any recent update for Matlab that you recall ?

– Sergiy Kolodyazhnyy
1 hour ago










1 Answer
1






active

oldest

votes


















0














In this case nohup [CMD] & is a good alternative. nohup frees the command from the terminal running it and makes it immune to terminal hangups.



Also, the command you posted opens a new session and immediately sends EOF with </dev/null which forces matlab to not accept any input from terminal. This might be an issue depending on how a given program executes upon opening. I also do not think disown serves any purpose here, as the & runs it in the background and setsid should free it from the terminal. disown does not disconnect the program from the terminal, it only removes it from the job list. In any case, I'd use nohup [CMD] & as it does



1) separate the program from the terminal running it



2) closes standard input



3) redirects stdout and stderr to a separate file for examination instead of just sending it into the /dev/null abyss



4) & at the end puts it in the background






share|improve this answer










New contributor




BarBar1234 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.




















    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "89"
    };
    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: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    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
    });


    }
    });






    Shaikat Saha is a new contributor. Be nice, and check out our Code of Conduct.










    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1119687%2frun-application-using-command-without-blocking-terminal%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    In this case nohup [CMD] & is a good alternative. nohup frees the command from the terminal running it and makes it immune to terminal hangups.



    Also, the command you posted opens a new session and immediately sends EOF with </dev/null which forces matlab to not accept any input from terminal. This might be an issue depending on how a given program executes upon opening. I also do not think disown serves any purpose here, as the & runs it in the background and setsid should free it from the terminal. disown does not disconnect the program from the terminal, it only removes it from the job list. In any case, I'd use nohup [CMD] & as it does



    1) separate the program from the terminal running it



    2) closes standard input



    3) redirects stdout and stderr to a separate file for examination instead of just sending it into the /dev/null abyss



    4) & at the end puts it in the background






    share|improve this answer










    New contributor




    BarBar1234 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.

























      0














      In this case nohup [CMD] & is a good alternative. nohup frees the command from the terminal running it and makes it immune to terminal hangups.



      Also, the command you posted opens a new session and immediately sends EOF with </dev/null which forces matlab to not accept any input from terminal. This might be an issue depending on how a given program executes upon opening. I also do not think disown serves any purpose here, as the & runs it in the background and setsid should free it from the terminal. disown does not disconnect the program from the terminal, it only removes it from the job list. In any case, I'd use nohup [CMD] & as it does



      1) separate the program from the terminal running it



      2) closes standard input



      3) redirects stdout and stderr to a separate file for examination instead of just sending it into the /dev/null abyss



      4) & at the end puts it in the background






      share|improve this answer










      New contributor




      BarBar1234 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.























        0












        0








        0







        In this case nohup [CMD] & is a good alternative. nohup frees the command from the terminal running it and makes it immune to terminal hangups.



        Also, the command you posted opens a new session and immediately sends EOF with </dev/null which forces matlab to not accept any input from terminal. This might be an issue depending on how a given program executes upon opening. I also do not think disown serves any purpose here, as the & runs it in the background and setsid should free it from the terminal. disown does not disconnect the program from the terminal, it only removes it from the job list. In any case, I'd use nohup [CMD] & as it does



        1) separate the program from the terminal running it



        2) closes standard input



        3) redirects stdout and stderr to a separate file for examination instead of just sending it into the /dev/null abyss



        4) & at the end puts it in the background






        share|improve this answer










        New contributor




        BarBar1234 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.










        In this case nohup [CMD] & is a good alternative. nohup frees the command from the terminal running it and makes it immune to terminal hangups.



        Also, the command you posted opens a new session and immediately sends EOF with </dev/null which forces matlab to not accept any input from terminal. This might be an issue depending on how a given program executes upon opening. I also do not think disown serves any purpose here, as the & runs it in the background and setsid should free it from the terminal. disown does not disconnect the program from the terminal, it only removes it from the job list. In any case, I'd use nohup [CMD] & as it does



        1) separate the program from the terminal running it



        2) closes standard input



        3) redirects stdout and stderr to a separate file for examination instead of just sending it into the /dev/null abyss



        4) & at the end puts it in the background







        share|improve this answer










        New contributor




        BarBar1234 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.









        share|improve this answer



        share|improve this answer








        edited 1 hour ago





















        New contributor




        BarBar1234 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.









        answered 1 hour ago









        BarBar1234BarBar1234

        212




        212




        New contributor




        BarBar1234 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.





        New contributor





        BarBar1234 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.






        BarBar1234 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.






















            Shaikat Saha is a new contributor. Be nice, and check out our Code of Conduct.










            draft saved

            draft discarded


















            Shaikat Saha is a new contributor. Be nice, and check out our Code of Conduct.













            Shaikat Saha is a new contributor. Be nice, and check out our Code of Conduct.












            Shaikat Saha is a new contributor. Be nice, and check out our Code of Conduct.
















            Thanks for contributing an answer to Ask Ubuntu!


            • 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%2faskubuntu.com%2fquestions%2f1119687%2frun-application-using-command-without-blocking-terminal%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







            Popular posts from this blog

            GameSpot

            日野市

            Tu-95轟炸機