how to know the status of a command?












1














How to tell whether previous command was successfully carried out or not.



I know one way is to use echo $? command:



[username@hostname ~]$ echo $?
0


But what about a scenario like this: say I want to run a python script called "ROSE_main.py"



[username@hostname rose]$ python ROSE_main.py -g HG18 -i HG18_MM1S_MED1.gff -r MM1S_MED1.hg18.bwt.sorted.bam -c MM1S_WCE.hg18.bwt.sorted.bam -o example -s 12500 -t 2500
USING HG18_MM1S_MED1.gff AS THE INPUT GFF
USING HG18 AS THE GENOME
MAKING START DICT
LOADING IN GFF REGIONS
CHECKING INPUT TO MAKE SURE EACH REGION HAS A UNIQUE IDENTIFIER
REFERENCE COLLECTION PASSES QC
STITCHING REGIONS TOGETHER
PERFORMING REGION STITCHING
REMOVED 7865 LOCI BECAUSE THEY WERE CONTAINED BY A TSS

...


The command seems to be executed like forever.
When I used "top" command in a new tap, here is what I see:



   315 root      RT   0     0    0    0 S 100.0  0.0   1801:10 migration/104                                                                                                                    
42 root RT 0 0 0 0 S 100.0 0.0 2023:48 migration/13
177 root RT 0 0 0 0 S 100.0 0.0 1622:39 migration/58
51 root RT 0 0 0 0 S 100.0 0.0 1820:09 migration/16
66 root RT 0 0 0 0 R 100.0 0.0 2135:56 migration/21
462 root RT 0 0 0 0 R 100.0 0.0 1696:18 migration/153
63 root RT 0 0 0 0 S 100.0 0.0 1735:34 migration/20
54 root RT 0 0 0 0 S 100.0 0.0 1844:20 migration/17
429 root RT 0 0 0 0 S 100.0 0.0 1690:33 migration/142
11471 gdm 20 0 374m 12m 4544 R 117.1 0.0 934:51.45 gnome-settings-
318 root RT 0 0 0 0 S 100.0 0.0 1774:44 migration/105


I guess if the command is still actively running, I should be able to see my username and something like "python", but instead, I saw nothing like that.



When I came to the command tap, the cursor was always flashing, so the command is still being executed, how could that be?



How could I know whether the command is still running?



top command did not give me any information.
Neither could I use echo $? (if I tried to input echo $?,
I will get some feedback such as pipeline broken)










share|improve this question
























  • If you got pipeline broken when you entered something on the command line, it means that the command was waiting for input from stdin.
    – RealSkeptic
    May 2 '16 at 9:48










  • Thanks, RealSkeptic. So the command is not dead. Do you think it is better to just wait? Also, is there any way to know the running condition, instead of passively waiting and praying?
    – Jun
    May 2 '16 at 9:53










  • Try using ps -ef to list all processes that are running, rather than top which just shows the top processes.
    – steve
    May 2 '16 at 9:54










  • 'Myusername 498271 464873 0 19:00 pts/33 00:00:00 ps -ef Mysusername 498361 465108 0 19:00 pts/26 00:00:00 /bin/sh -c samtools view MM1S_WCE.hg18.bwt.sorted.bam chr15:79190228-79191852 Myusername 498374 465104 0 19:00 pts/26 00:00:00 samtools view MM1S_MED1.hg18.bwt.sorted.bam chr15:44424045-44425235 myusername 498375 465106 0 19:00 pts/26 00:00:00 samtools view MM1S_MED1.hg18.bwt.sorted.bam chr5:36186618-36188852' Yes, I could see the running processes. Tsk! steve.
    – Jun
    May 2 '16 at 10:03


















1














How to tell whether previous command was successfully carried out or not.



I know one way is to use echo $? command:



[username@hostname ~]$ echo $?
0


But what about a scenario like this: say I want to run a python script called "ROSE_main.py"



[username@hostname rose]$ python ROSE_main.py -g HG18 -i HG18_MM1S_MED1.gff -r MM1S_MED1.hg18.bwt.sorted.bam -c MM1S_WCE.hg18.bwt.sorted.bam -o example -s 12500 -t 2500
USING HG18_MM1S_MED1.gff AS THE INPUT GFF
USING HG18 AS THE GENOME
MAKING START DICT
LOADING IN GFF REGIONS
CHECKING INPUT TO MAKE SURE EACH REGION HAS A UNIQUE IDENTIFIER
REFERENCE COLLECTION PASSES QC
STITCHING REGIONS TOGETHER
PERFORMING REGION STITCHING
REMOVED 7865 LOCI BECAUSE THEY WERE CONTAINED BY A TSS

...


The command seems to be executed like forever.
When I used "top" command in a new tap, here is what I see:



   315 root      RT   0     0    0    0 S 100.0  0.0   1801:10 migration/104                                                                                                                    
42 root RT 0 0 0 0 S 100.0 0.0 2023:48 migration/13
177 root RT 0 0 0 0 S 100.0 0.0 1622:39 migration/58
51 root RT 0 0 0 0 S 100.0 0.0 1820:09 migration/16
66 root RT 0 0 0 0 R 100.0 0.0 2135:56 migration/21
462 root RT 0 0 0 0 R 100.0 0.0 1696:18 migration/153
63 root RT 0 0 0 0 S 100.0 0.0 1735:34 migration/20
54 root RT 0 0 0 0 S 100.0 0.0 1844:20 migration/17
429 root RT 0 0 0 0 S 100.0 0.0 1690:33 migration/142
11471 gdm 20 0 374m 12m 4544 R 117.1 0.0 934:51.45 gnome-settings-
318 root RT 0 0 0 0 S 100.0 0.0 1774:44 migration/105


I guess if the command is still actively running, I should be able to see my username and something like "python", but instead, I saw nothing like that.



When I came to the command tap, the cursor was always flashing, so the command is still being executed, how could that be?



How could I know whether the command is still running?



top command did not give me any information.
Neither could I use echo $? (if I tried to input echo $?,
I will get some feedback such as pipeline broken)










share|improve this question
























  • If you got pipeline broken when you entered something on the command line, it means that the command was waiting for input from stdin.
    – RealSkeptic
    May 2 '16 at 9:48










  • Thanks, RealSkeptic. So the command is not dead. Do you think it is better to just wait? Also, is there any way to know the running condition, instead of passively waiting and praying?
    – Jun
    May 2 '16 at 9:53










  • Try using ps -ef to list all processes that are running, rather than top which just shows the top processes.
    – steve
    May 2 '16 at 9:54










  • 'Myusername 498271 464873 0 19:00 pts/33 00:00:00 ps -ef Mysusername 498361 465108 0 19:00 pts/26 00:00:00 /bin/sh -c samtools view MM1S_WCE.hg18.bwt.sorted.bam chr15:79190228-79191852 Myusername 498374 465104 0 19:00 pts/26 00:00:00 samtools view MM1S_MED1.hg18.bwt.sorted.bam chr15:44424045-44425235 myusername 498375 465106 0 19:00 pts/26 00:00:00 samtools view MM1S_MED1.hg18.bwt.sorted.bam chr5:36186618-36188852' Yes, I could see the running processes. Tsk! steve.
    – Jun
    May 2 '16 at 10:03
















1












1








1







How to tell whether previous command was successfully carried out or not.



I know one way is to use echo $? command:



[username@hostname ~]$ echo $?
0


But what about a scenario like this: say I want to run a python script called "ROSE_main.py"



[username@hostname rose]$ python ROSE_main.py -g HG18 -i HG18_MM1S_MED1.gff -r MM1S_MED1.hg18.bwt.sorted.bam -c MM1S_WCE.hg18.bwt.sorted.bam -o example -s 12500 -t 2500
USING HG18_MM1S_MED1.gff AS THE INPUT GFF
USING HG18 AS THE GENOME
MAKING START DICT
LOADING IN GFF REGIONS
CHECKING INPUT TO MAKE SURE EACH REGION HAS A UNIQUE IDENTIFIER
REFERENCE COLLECTION PASSES QC
STITCHING REGIONS TOGETHER
PERFORMING REGION STITCHING
REMOVED 7865 LOCI BECAUSE THEY WERE CONTAINED BY A TSS

...


The command seems to be executed like forever.
When I used "top" command in a new tap, here is what I see:



   315 root      RT   0     0    0    0 S 100.0  0.0   1801:10 migration/104                                                                                                                    
42 root RT 0 0 0 0 S 100.0 0.0 2023:48 migration/13
177 root RT 0 0 0 0 S 100.0 0.0 1622:39 migration/58
51 root RT 0 0 0 0 S 100.0 0.0 1820:09 migration/16
66 root RT 0 0 0 0 R 100.0 0.0 2135:56 migration/21
462 root RT 0 0 0 0 R 100.0 0.0 1696:18 migration/153
63 root RT 0 0 0 0 S 100.0 0.0 1735:34 migration/20
54 root RT 0 0 0 0 S 100.0 0.0 1844:20 migration/17
429 root RT 0 0 0 0 S 100.0 0.0 1690:33 migration/142
11471 gdm 20 0 374m 12m 4544 R 117.1 0.0 934:51.45 gnome-settings-
318 root RT 0 0 0 0 S 100.0 0.0 1774:44 migration/105


I guess if the command is still actively running, I should be able to see my username and something like "python", but instead, I saw nothing like that.



When I came to the command tap, the cursor was always flashing, so the command is still being executed, how could that be?



How could I know whether the command is still running?



top command did not give me any information.
Neither could I use echo $? (if I tried to input echo $?,
I will get some feedback such as pipeline broken)










share|improve this question















How to tell whether previous command was successfully carried out or not.



I know one way is to use echo $? command:



[username@hostname ~]$ echo $?
0


But what about a scenario like this: say I want to run a python script called "ROSE_main.py"



[username@hostname rose]$ python ROSE_main.py -g HG18 -i HG18_MM1S_MED1.gff -r MM1S_MED1.hg18.bwt.sorted.bam -c MM1S_WCE.hg18.bwt.sorted.bam -o example -s 12500 -t 2500
USING HG18_MM1S_MED1.gff AS THE INPUT GFF
USING HG18 AS THE GENOME
MAKING START DICT
LOADING IN GFF REGIONS
CHECKING INPUT TO MAKE SURE EACH REGION HAS A UNIQUE IDENTIFIER
REFERENCE COLLECTION PASSES QC
STITCHING REGIONS TOGETHER
PERFORMING REGION STITCHING
REMOVED 7865 LOCI BECAUSE THEY WERE CONTAINED BY A TSS

...


The command seems to be executed like forever.
When I used "top" command in a new tap, here is what I see:



   315 root      RT   0     0    0    0 S 100.0  0.0   1801:10 migration/104                                                                                                                    
42 root RT 0 0 0 0 S 100.0 0.0 2023:48 migration/13
177 root RT 0 0 0 0 S 100.0 0.0 1622:39 migration/58
51 root RT 0 0 0 0 S 100.0 0.0 1820:09 migration/16
66 root RT 0 0 0 0 R 100.0 0.0 2135:56 migration/21
462 root RT 0 0 0 0 R 100.0 0.0 1696:18 migration/153
63 root RT 0 0 0 0 S 100.0 0.0 1735:34 migration/20
54 root RT 0 0 0 0 S 100.0 0.0 1844:20 migration/17
429 root RT 0 0 0 0 S 100.0 0.0 1690:33 migration/142
11471 gdm 20 0 374m 12m 4544 R 117.1 0.0 934:51.45 gnome-settings-
318 root RT 0 0 0 0 S 100.0 0.0 1774:44 migration/105


I guess if the command is still actively running, I should be able to see my username and something like "python", but instead, I saw nothing like that.



When I came to the command tap, the cursor was always flashing, so the command is still being executed, how could that be?



How could I know whether the command is still running?



top command did not give me any information.
Neither could I use echo $? (if I tried to input echo $?,
I will get some feedback such as pipeline broken)







linux command






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Dec 15 at 16:58









Rui F Ribeiro

38.9k1479129




38.9k1479129










asked May 2 '16 at 9:42









Jun

3262618




3262618












  • If you got pipeline broken when you entered something on the command line, it means that the command was waiting for input from stdin.
    – RealSkeptic
    May 2 '16 at 9:48










  • Thanks, RealSkeptic. So the command is not dead. Do you think it is better to just wait? Also, is there any way to know the running condition, instead of passively waiting and praying?
    – Jun
    May 2 '16 at 9:53










  • Try using ps -ef to list all processes that are running, rather than top which just shows the top processes.
    – steve
    May 2 '16 at 9:54










  • 'Myusername 498271 464873 0 19:00 pts/33 00:00:00 ps -ef Mysusername 498361 465108 0 19:00 pts/26 00:00:00 /bin/sh -c samtools view MM1S_WCE.hg18.bwt.sorted.bam chr15:79190228-79191852 Myusername 498374 465104 0 19:00 pts/26 00:00:00 samtools view MM1S_MED1.hg18.bwt.sorted.bam chr15:44424045-44425235 myusername 498375 465106 0 19:00 pts/26 00:00:00 samtools view MM1S_MED1.hg18.bwt.sorted.bam chr5:36186618-36188852' Yes, I could see the running processes. Tsk! steve.
    – Jun
    May 2 '16 at 10:03




















  • If you got pipeline broken when you entered something on the command line, it means that the command was waiting for input from stdin.
    – RealSkeptic
    May 2 '16 at 9:48










  • Thanks, RealSkeptic. So the command is not dead. Do you think it is better to just wait? Also, is there any way to know the running condition, instead of passively waiting and praying?
    – Jun
    May 2 '16 at 9:53










  • Try using ps -ef to list all processes that are running, rather than top which just shows the top processes.
    – steve
    May 2 '16 at 9:54










  • 'Myusername 498271 464873 0 19:00 pts/33 00:00:00 ps -ef Mysusername 498361 465108 0 19:00 pts/26 00:00:00 /bin/sh -c samtools view MM1S_WCE.hg18.bwt.sorted.bam chr15:79190228-79191852 Myusername 498374 465104 0 19:00 pts/26 00:00:00 samtools view MM1S_MED1.hg18.bwt.sorted.bam chr15:44424045-44425235 myusername 498375 465106 0 19:00 pts/26 00:00:00 samtools view MM1S_MED1.hg18.bwt.sorted.bam chr5:36186618-36188852' Yes, I could see the running processes. Tsk! steve.
    – Jun
    May 2 '16 at 10:03


















If you got pipeline broken when you entered something on the command line, it means that the command was waiting for input from stdin.
– RealSkeptic
May 2 '16 at 9:48




If you got pipeline broken when you entered something on the command line, it means that the command was waiting for input from stdin.
– RealSkeptic
May 2 '16 at 9:48












Thanks, RealSkeptic. So the command is not dead. Do you think it is better to just wait? Also, is there any way to know the running condition, instead of passively waiting and praying?
– Jun
May 2 '16 at 9:53




Thanks, RealSkeptic. So the command is not dead. Do you think it is better to just wait? Also, is there any way to know the running condition, instead of passively waiting and praying?
– Jun
May 2 '16 at 9:53












Try using ps -ef to list all processes that are running, rather than top which just shows the top processes.
– steve
May 2 '16 at 9:54




Try using ps -ef to list all processes that are running, rather than top which just shows the top processes.
– steve
May 2 '16 at 9:54












'Myusername 498271 464873 0 19:00 pts/33 00:00:00 ps -ef Mysusername 498361 465108 0 19:00 pts/26 00:00:00 /bin/sh -c samtools view MM1S_WCE.hg18.bwt.sorted.bam chr15:79190228-79191852 Myusername 498374 465104 0 19:00 pts/26 00:00:00 samtools view MM1S_MED1.hg18.bwt.sorted.bam chr15:44424045-44425235 myusername 498375 465106 0 19:00 pts/26 00:00:00 samtools view MM1S_MED1.hg18.bwt.sorted.bam chr5:36186618-36188852' Yes, I could see the running processes. Tsk! steve.
– Jun
May 2 '16 at 10:03






'Myusername 498271 464873 0 19:00 pts/33 00:00:00 ps -ef Mysusername 498361 465108 0 19:00 pts/26 00:00:00 /bin/sh -c samtools view MM1S_WCE.hg18.bwt.sorted.bam chr15:79190228-79191852 Myusername 498374 465104 0 19:00 pts/26 00:00:00 samtools view MM1S_MED1.hg18.bwt.sorted.bam chr15:44424045-44425235 myusername 498375 465106 0 19:00 pts/26 00:00:00 samtools view MM1S_MED1.hg18.bwt.sorted.bam chr5:36186618-36188852' Yes, I could see the running processes. Tsk! steve.
– Jun
May 2 '16 at 10:03












1 Answer
1






active

oldest

votes


















2














If the command died, you'd get the shell prompt back, with or without an error message.



So in any case, it is still running. But in your case, it seems to be waiting for input from the terminal. This usually means that it will never end, unless you give it the input that it is waiting for.



In any case, top is not the right tool. It is meant to show the top processes - either the ones that use most CPU, most memory, etc. - and your command isn't necessarily one of the processes that rank highest in any category that top sorts by.



The proper tool to see the status of a command is ps. You can use ps to show all the processes in the system (with -e), only your own (or a particular user's) processes (with -U), or specific processes. Other parameters to ps are defining its format. So in your case you could use



ps -lf $(pgrep python)


To see all the processes whose head command is python.



The -lf gives you a lot of information about each such process - among them the state of the process (under the column S), and if it's currently sleeping rather than running, the system call where it has stopped (WCHAN).



If the command is running, rather than waiting, you'd see R in the S column, and - in the WCHAN column. If it's waiting for something, you'd see S in the S column, and something like wait_w, poll_s, futex_ etc. in the WCHAN column.



It's hard to say what it is waiting for exactly, but if you see that it stays in that state for a long time and you were expecting it to start running, you should check the command itself to see if you ran it correctly.



Read the ps manual for further details about the possible formats and what you can see in its output.



And as for your python command, you should check to see why it is waiting for user input.






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%2f280539%2fhow-to-know-the-status-of-a-command%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









    2














    If the command died, you'd get the shell prompt back, with or without an error message.



    So in any case, it is still running. But in your case, it seems to be waiting for input from the terminal. This usually means that it will never end, unless you give it the input that it is waiting for.



    In any case, top is not the right tool. It is meant to show the top processes - either the ones that use most CPU, most memory, etc. - and your command isn't necessarily one of the processes that rank highest in any category that top sorts by.



    The proper tool to see the status of a command is ps. You can use ps to show all the processes in the system (with -e), only your own (or a particular user's) processes (with -U), or specific processes. Other parameters to ps are defining its format. So in your case you could use



    ps -lf $(pgrep python)


    To see all the processes whose head command is python.



    The -lf gives you a lot of information about each such process - among them the state of the process (under the column S), and if it's currently sleeping rather than running, the system call where it has stopped (WCHAN).



    If the command is running, rather than waiting, you'd see R in the S column, and - in the WCHAN column. If it's waiting for something, you'd see S in the S column, and something like wait_w, poll_s, futex_ etc. in the WCHAN column.



    It's hard to say what it is waiting for exactly, but if you see that it stays in that state for a long time and you were expecting it to start running, you should check the command itself to see if you ran it correctly.



    Read the ps manual for further details about the possible formats and what you can see in its output.



    And as for your python command, you should check to see why it is waiting for user input.






    share|improve this answer




























      2














      If the command died, you'd get the shell prompt back, with or without an error message.



      So in any case, it is still running. But in your case, it seems to be waiting for input from the terminal. This usually means that it will never end, unless you give it the input that it is waiting for.



      In any case, top is not the right tool. It is meant to show the top processes - either the ones that use most CPU, most memory, etc. - and your command isn't necessarily one of the processes that rank highest in any category that top sorts by.



      The proper tool to see the status of a command is ps. You can use ps to show all the processes in the system (with -e), only your own (or a particular user's) processes (with -U), or specific processes. Other parameters to ps are defining its format. So in your case you could use



      ps -lf $(pgrep python)


      To see all the processes whose head command is python.



      The -lf gives you a lot of information about each such process - among them the state of the process (under the column S), and if it's currently sleeping rather than running, the system call where it has stopped (WCHAN).



      If the command is running, rather than waiting, you'd see R in the S column, and - in the WCHAN column. If it's waiting for something, you'd see S in the S column, and something like wait_w, poll_s, futex_ etc. in the WCHAN column.



      It's hard to say what it is waiting for exactly, but if you see that it stays in that state for a long time and you were expecting it to start running, you should check the command itself to see if you ran it correctly.



      Read the ps manual for further details about the possible formats and what you can see in its output.



      And as for your python command, you should check to see why it is waiting for user input.






      share|improve this answer


























        2












        2








        2






        If the command died, you'd get the shell prompt back, with or without an error message.



        So in any case, it is still running. But in your case, it seems to be waiting for input from the terminal. This usually means that it will never end, unless you give it the input that it is waiting for.



        In any case, top is not the right tool. It is meant to show the top processes - either the ones that use most CPU, most memory, etc. - and your command isn't necessarily one of the processes that rank highest in any category that top sorts by.



        The proper tool to see the status of a command is ps. You can use ps to show all the processes in the system (with -e), only your own (or a particular user's) processes (with -U), or specific processes. Other parameters to ps are defining its format. So in your case you could use



        ps -lf $(pgrep python)


        To see all the processes whose head command is python.



        The -lf gives you a lot of information about each such process - among them the state of the process (under the column S), and if it's currently sleeping rather than running, the system call where it has stopped (WCHAN).



        If the command is running, rather than waiting, you'd see R in the S column, and - in the WCHAN column. If it's waiting for something, you'd see S in the S column, and something like wait_w, poll_s, futex_ etc. in the WCHAN column.



        It's hard to say what it is waiting for exactly, but if you see that it stays in that state for a long time and you were expecting it to start running, you should check the command itself to see if you ran it correctly.



        Read the ps manual for further details about the possible formats and what you can see in its output.



        And as for your python command, you should check to see why it is waiting for user input.






        share|improve this answer














        If the command died, you'd get the shell prompt back, with or without an error message.



        So in any case, it is still running. But in your case, it seems to be waiting for input from the terminal. This usually means that it will never end, unless you give it the input that it is waiting for.



        In any case, top is not the right tool. It is meant to show the top processes - either the ones that use most CPU, most memory, etc. - and your command isn't necessarily one of the processes that rank highest in any category that top sorts by.



        The proper tool to see the status of a command is ps. You can use ps to show all the processes in the system (with -e), only your own (or a particular user's) processes (with -U), or specific processes. Other parameters to ps are defining its format. So in your case you could use



        ps -lf $(pgrep python)


        To see all the processes whose head command is python.



        The -lf gives you a lot of information about each such process - among them the state of the process (under the column S), and if it's currently sleeping rather than running, the system call where it has stopped (WCHAN).



        If the command is running, rather than waiting, you'd see R in the S column, and - in the WCHAN column. If it's waiting for something, you'd see S in the S column, and something like wait_w, poll_s, futex_ etc. in the WCHAN column.



        It's hard to say what it is waiting for exactly, but if you see that it stays in that state for a long time and you were expecting it to start running, you should check the command itself to see if you ran it correctly.



        Read the ps manual for further details about the possible formats and what you can see in its output.



        And as for your python command, you should check to see why it is waiting for user input.







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited May 2 '16 at 10:16

























        answered May 2 '16 at 10:09









        RealSkeptic

        762411




        762411






























            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.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • 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%2f280539%2fhow-to-know-the-status-of-a-command%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

            Morgemoulin

            Scott Moir

            Souastre