trying to use nohup but keep getting another windows to show up

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
0
down vote

favorite












i want to launch windows 10 from virtualbox and i'm created a shortcut to my desktop and click on proprieties to get the commend line to start windows 10 from a menu, so i put the command in the command line using nohup so the terminal will close after it starts but i keep getting another terminal open with the nohup: ignoring input and appending output to 'nohup.out' err how can i get rid of this windows from showing up?










share|improve this question





















  • Can you edit your question to contain the contents of the desktop shortcut? The file is named something like ~/Desktop/foo.desktop.You probably just need to edit it to change Terminal=true to Terminal=false
    – Mark Plotnick
    Oct 9 '17 at 19:20















up vote
0
down vote

favorite












i want to launch windows 10 from virtualbox and i'm created a shortcut to my desktop and click on proprieties to get the commend line to start windows 10 from a menu, so i put the command in the command line using nohup so the terminal will close after it starts but i keep getting another terminal open with the nohup: ignoring input and appending output to 'nohup.out' err how can i get rid of this windows from showing up?










share|improve this question





















  • Can you edit your question to contain the contents of the desktop shortcut? The file is named something like ~/Desktop/foo.desktop.You probably just need to edit it to change Terminal=true to Terminal=false
    – Mark Plotnick
    Oct 9 '17 at 19:20













up vote
0
down vote

favorite









up vote
0
down vote

favorite











i want to launch windows 10 from virtualbox and i'm created a shortcut to my desktop and click on proprieties to get the commend line to start windows 10 from a menu, so i put the command in the command line using nohup so the terminal will close after it starts but i keep getting another terminal open with the nohup: ignoring input and appending output to 'nohup.out' err how can i get rid of this windows from showing up?










share|improve this question













i want to launch windows 10 from virtualbox and i'm created a shortcut to my desktop and click on proprieties to get the commend line to start windows 10 from a menu, so i put the command in the command line using nohup so the terminal will close after it starts but i keep getting another terminal open with the nohup: ignoring input and appending output to 'nohup.out' err how can i get rid of this windows from showing up?







nohup






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Oct 9 '17 at 12:44









user254745

1




1











  • Can you edit your question to contain the contents of the desktop shortcut? The file is named something like ~/Desktop/foo.desktop.You probably just need to edit it to change Terminal=true to Terminal=false
    – Mark Plotnick
    Oct 9 '17 at 19:20

















  • Can you edit your question to contain the contents of the desktop shortcut? The file is named something like ~/Desktop/foo.desktop.You probably just need to edit it to change Terminal=true to Terminal=false
    – Mark Plotnick
    Oct 9 '17 at 19:20
















Can you edit your question to contain the contents of the desktop shortcut? The file is named something like ~/Desktop/foo.desktop.You probably just need to edit it to change Terminal=true to Terminal=false
– Mark Plotnick
Oct 9 '17 at 19:20





Can you edit your question to contain the contents of the desktop shortcut? The file is named something like ~/Desktop/foo.desktop.You probably just need to edit it to change Terminal=true to Terminal=false
– Mark Plotnick
Oct 9 '17 at 19:20











1 Answer
1






active

oldest

votes

















up vote
0
down vote













To get nohup to "shutup" stdin, stdout and stderr all need to be explicitly directed from/to somewhere. So you could do this:



nohup cmd </dev/null >/dev/null 2>&1


But a simpler solution is to just redirect stderr since that's where the warning is coming from:



nohup cmd 2>/dev/null


Now I don't know if this will prevent the window from popping but it's a place to start. Try the short version. If that doesn't work try the first version. If neither work then we'll at least know a little more than we do now.






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',
    convertImagesToLinks: false,
    noModals: false,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    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%2f397010%2ftrying-to-use-nohup-but-keep-getting-another-windows-to-show-up%23new-answer', 'question_page');

    );

    Post as a guest






























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    0
    down vote













    To get nohup to "shutup" stdin, stdout and stderr all need to be explicitly directed from/to somewhere. So you could do this:



    nohup cmd </dev/null >/dev/null 2>&1


    But a simpler solution is to just redirect stderr since that's where the warning is coming from:



    nohup cmd 2>/dev/null


    Now I don't know if this will prevent the window from popping but it's a place to start. Try the short version. If that doesn't work try the first version. If neither work then we'll at least know a little more than we do now.






    share|improve this answer


























      up vote
      0
      down vote













      To get nohup to "shutup" stdin, stdout and stderr all need to be explicitly directed from/to somewhere. So you could do this:



      nohup cmd </dev/null >/dev/null 2>&1


      But a simpler solution is to just redirect stderr since that's where the warning is coming from:



      nohup cmd 2>/dev/null


      Now I don't know if this will prevent the window from popping but it's a place to start. Try the short version. If that doesn't work try the first version. If neither work then we'll at least know a little more than we do now.






      share|improve this answer
























        up vote
        0
        down vote










        up vote
        0
        down vote









        To get nohup to "shutup" stdin, stdout and stderr all need to be explicitly directed from/to somewhere. So you could do this:



        nohup cmd </dev/null >/dev/null 2>&1


        But a simpler solution is to just redirect stderr since that's where the warning is coming from:



        nohup cmd 2>/dev/null


        Now I don't know if this will prevent the window from popping but it's a place to start. Try the short version. If that doesn't work try the first version. If neither work then we'll at least know a little more than we do now.






        share|improve this answer














        To get nohup to "shutup" stdin, stdout and stderr all need to be explicitly directed from/to somewhere. So you could do this:



        nohup cmd </dev/null >/dev/null 2>&1


        But a simpler solution is to just redirect stderr since that's where the warning is coming from:



        nohup cmd 2>/dev/null


        Now I don't know if this will prevent the window from popping but it's a place to start. Try the short version. If that doesn't work try the first version. If neither work then we'll at least know a little more than we do now.







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Oct 9 '17 at 13:34

























        answered Oct 9 '17 at 13:21









        B Layer

        3,9241525




        3,9241525



























             

            draft saved


            draft discarded















































             


            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f397010%2ftrying-to-use-nohup-but-keep-getting-another-windows-to-show-up%23new-answer', 'question_page');

            );

            Post as a guest













































































            Popular posts from this blog

            How to check contact read email or not when send email to Individual?

            Displaying single band from multi-band raster using QGIS

            How many registers does an x86_64 CPU actually have?