How to terminate ping &












8















The command



ping <dest> &


causes ping to go to the background. It still prints output to the terminal, however. Ctrl-C does not stop it, only introduces a new prompt. How to stop it from the terminal?










share|improve this question









New contributor




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





















  • In addition to the answers, there is a way to naturally limit ping's iterations with a count — -c N — where N is a positive number.

    – l0b0
    yesterday













  • @l0b0 Yes true, but I faced this particular problem, and it's actually related to any program where we might not know the execution time, or where it might not even be defined. So I mean to ask how to stop the process.

    – Vineet
    yesterday











  • Nitpick: It's not a URL.

    – Roger Lipscombe
    yesterday











  • @RogerLipscombe What do you call it, other than destination? Host is a little unsure, considering that a single computer may host many domains

    – Vineet
    yesterday











  • It's a hostname (or an IP address). "a single computer may host many domains" -- not relevant to ping.

    – Roger Lipscombe
    yesterday
















8















The command



ping <dest> &


causes ping to go to the background. It still prints output to the terminal, however. Ctrl-C does not stop it, only introduces a new prompt. How to stop it from the terminal?










share|improve this question









New contributor




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





















  • In addition to the answers, there is a way to naturally limit ping's iterations with a count — -c N — where N is a positive number.

    – l0b0
    yesterday













  • @l0b0 Yes true, but I faced this particular problem, and it's actually related to any program where we might not know the execution time, or where it might not even be defined. So I mean to ask how to stop the process.

    – Vineet
    yesterday











  • Nitpick: It's not a URL.

    – Roger Lipscombe
    yesterday











  • @RogerLipscombe What do you call it, other than destination? Host is a little unsure, considering that a single computer may host many domains

    – Vineet
    yesterday











  • It's a hostname (or an IP address). "a single computer may host many domains" -- not relevant to ping.

    – Roger Lipscombe
    yesterday














8












8








8








The command



ping <dest> &


causes ping to go to the background. It still prints output to the terminal, however. Ctrl-C does not stop it, only introduces a new prompt. How to stop it from the terminal?










share|improve this question









New contributor




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












The command



ping <dest> &


causes ping to go to the background. It still prints output to the terminal, however. Ctrl-C does not stop it, only introduces a new prompt. How to stop it from the terminal?







command-line






share|improve this question









New contributor




Vineet 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




Vineet 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








edited yesterday







Vineet













New contributor




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









asked yesterday









VineetVineet

436




436




New contributor




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





New contributor





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






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













  • In addition to the answers, there is a way to naturally limit ping's iterations with a count — -c N — where N is a positive number.

    – l0b0
    yesterday













  • @l0b0 Yes true, but I faced this particular problem, and it's actually related to any program where we might not know the execution time, or where it might not even be defined. So I mean to ask how to stop the process.

    – Vineet
    yesterday











  • Nitpick: It's not a URL.

    – Roger Lipscombe
    yesterday











  • @RogerLipscombe What do you call it, other than destination? Host is a little unsure, considering that a single computer may host many domains

    – Vineet
    yesterday











  • It's a hostname (or an IP address). "a single computer may host many domains" -- not relevant to ping.

    – Roger Lipscombe
    yesterday



















  • In addition to the answers, there is a way to naturally limit ping's iterations with a count — -c N — where N is a positive number.

    – l0b0
    yesterday













  • @l0b0 Yes true, but I faced this particular problem, and it's actually related to any program where we might not know the execution time, or where it might not even be defined. So I mean to ask how to stop the process.

    – Vineet
    yesterday











  • Nitpick: It's not a URL.

    – Roger Lipscombe
    yesterday











  • @RogerLipscombe What do you call it, other than destination? Host is a little unsure, considering that a single computer may host many domains

    – Vineet
    yesterday











  • It's a hostname (or an IP address). "a single computer may host many domains" -- not relevant to ping.

    – Roger Lipscombe
    yesterday

















In addition to the answers, there is a way to naturally limit ping's iterations with a count — -c N — where N is a positive number.

– l0b0
yesterday







In addition to the answers, there is a way to naturally limit ping's iterations with a count — -c N — where N is a positive number.

– l0b0
yesterday















@l0b0 Yes true, but I faced this particular problem, and it's actually related to any program where we might not know the execution time, or where it might not even be defined. So I mean to ask how to stop the process.

– Vineet
yesterday





@l0b0 Yes true, but I faced this particular problem, and it's actually related to any program where we might not know the execution time, or where it might not even be defined. So I mean to ask how to stop the process.

– Vineet
yesterday













Nitpick: It's not a URL.

– Roger Lipscombe
yesterday





Nitpick: It's not a URL.

– Roger Lipscombe
yesterday













@RogerLipscombe What do you call it, other than destination? Host is a little unsure, considering that a single computer may host many domains

– Vineet
yesterday





@RogerLipscombe What do you call it, other than destination? Host is a little unsure, considering that a single computer may host many domains

– Vineet
yesterday













It's a hostname (or an IP address). "a single computer may host many domains" -- not relevant to ping.

– Roger Lipscombe
yesterday





It's a hostname (or an IP address). "a single computer may host many domains" -- not relevant to ping.

– Roger Lipscombe
yesterday










5 Answers
5






active

oldest

votes


















15














First enter fg into same terminal that your ping command is running (it brings the process into the foreground), then press Ctrl+c to stop the process.



enter image description here






share|improve this answer


























  • This works. I also realized that fg works if we have multiple background processes, by calling them to the foreground one by one.

    – Vineet
    yesterday











  • Yep, that's how it works, you can use jobs to get a list of process that are running in background.

    – Ravexina
    yesterday











  • How did you make that image loop?

    – phillipsk
    11 hours ago











  • @phillipsk It's GIF, that's how GIF works ...

    – Ravexina
    11 hours ago



















10














If it is your one and only background job you can kill it with kill %1. If not sure you can list all your background jobs with jobs and use kill %<n> where you replace n by the number of your ping job.






share|improve this answer



















  • 3





    Also, I found out that n matches the number that is print out in square brackets when running the command.

    – Vineet
    yesterday



















3














Launch a new tab of terminal, run:



$ pgrep ping
2564


Then kill the pid using kill command:



$ kill 2564





share|improve this answer
























  • I used kill in the same terminal too (though the output made it difficult to use). However, I was wondering what to do if I couldn't go far back up in the terminal to see the process id printed, so pgrep has helped, additionally.

    – Vineet
    yesterday






  • 2





    When you use pgrep to search processes by name, you can also use pkill to kill them by name. No need to type/copy the process id and use kill.

    – Byte Commander
    yesterday



















3














When you send a process to the background, whether by using ctrl-z or by & at the end of the command, you get an output in the following format: [index] process-id. If you send multiple processes to the background, the index will keep incrementing every time.



For example:



$ sleep 100 &
[1] 41608
$ sleep 101 &
[2] 41609
$ sleep 102 &
[3] 41610
$ sleep 103 &
[4] 41611
$ sleep 104 &
[5] 41612
$ sleep 105 &
[6] 41613
$ sleep 106 &
[7] 41614


In order to stop a specific one, you can either use kill <process-id> or use fg <index> followed by ctrl-c



Example using the previous output:



$ kill 41614


or



$ fg 7
sleep 106
^C





share|improve this answer































    0














    When you are root, it's simply killall ping.






    share|improve this answer























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


      }
      });






      Vineet 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%2f1125926%2fhow-to-terminate-ping-dest%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      5 Answers
      5






      active

      oldest

      votes








      5 Answers
      5






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      15














      First enter fg into same terminal that your ping command is running (it brings the process into the foreground), then press Ctrl+c to stop the process.



      enter image description here






      share|improve this answer


























      • This works. I also realized that fg works if we have multiple background processes, by calling them to the foreground one by one.

        – Vineet
        yesterday











      • Yep, that's how it works, you can use jobs to get a list of process that are running in background.

        – Ravexina
        yesterday











      • How did you make that image loop?

        – phillipsk
        11 hours ago











      • @phillipsk It's GIF, that's how GIF works ...

        – Ravexina
        11 hours ago
















      15














      First enter fg into same terminal that your ping command is running (it brings the process into the foreground), then press Ctrl+c to stop the process.



      enter image description here






      share|improve this answer


























      • This works. I also realized that fg works if we have multiple background processes, by calling them to the foreground one by one.

        – Vineet
        yesterday











      • Yep, that's how it works, you can use jobs to get a list of process that are running in background.

        – Ravexina
        yesterday











      • How did you make that image loop?

        – phillipsk
        11 hours ago











      • @phillipsk It's GIF, that's how GIF works ...

        – Ravexina
        11 hours ago














      15












      15








      15







      First enter fg into same terminal that your ping command is running (it brings the process into the foreground), then press Ctrl+c to stop the process.



      enter image description here






      share|improve this answer















      First enter fg into same terminal that your ping command is running (it brings the process into the foreground), then press Ctrl+c to stop the process.



      enter image description here







      share|improve this answer














      share|improve this answer



      share|improve this answer








      edited yesterday

























      answered yesterday









      RavexinaRavexina

      32.9k1487114




      32.9k1487114













      • This works. I also realized that fg works if we have multiple background processes, by calling them to the foreground one by one.

        – Vineet
        yesterday











      • Yep, that's how it works, you can use jobs to get a list of process that are running in background.

        – Ravexina
        yesterday











      • How did you make that image loop?

        – phillipsk
        11 hours ago











      • @phillipsk It's GIF, that's how GIF works ...

        – Ravexina
        11 hours ago



















      • This works. I also realized that fg works if we have multiple background processes, by calling them to the foreground one by one.

        – Vineet
        yesterday











      • Yep, that's how it works, you can use jobs to get a list of process that are running in background.

        – Ravexina
        yesterday











      • How did you make that image loop?

        – phillipsk
        11 hours ago











      • @phillipsk It's GIF, that's how GIF works ...

        – Ravexina
        11 hours ago

















      This works. I also realized that fg works if we have multiple background processes, by calling them to the foreground one by one.

      – Vineet
      yesterday





      This works. I also realized that fg works if we have multiple background processes, by calling them to the foreground one by one.

      – Vineet
      yesterday













      Yep, that's how it works, you can use jobs to get a list of process that are running in background.

      – Ravexina
      yesterday





      Yep, that's how it works, you can use jobs to get a list of process that are running in background.

      – Ravexina
      yesterday













      How did you make that image loop?

      – phillipsk
      11 hours ago





      How did you make that image loop?

      – phillipsk
      11 hours ago













      @phillipsk It's GIF, that's how GIF works ...

      – Ravexina
      11 hours ago





      @phillipsk It's GIF, that's how GIF works ...

      – Ravexina
      11 hours ago













      10














      If it is your one and only background job you can kill it with kill %1. If not sure you can list all your background jobs with jobs and use kill %<n> where you replace n by the number of your ping job.






      share|improve this answer



















      • 3





        Also, I found out that n matches the number that is print out in square brackets when running the command.

        – Vineet
        yesterday
















      10














      If it is your one and only background job you can kill it with kill %1. If not sure you can list all your background jobs with jobs and use kill %<n> where you replace n by the number of your ping job.






      share|improve this answer



















      • 3





        Also, I found out that n matches the number that is print out in square brackets when running the command.

        – Vineet
        yesterday














      10












      10








      10







      If it is your one and only background job you can kill it with kill %1. If not sure you can list all your background jobs with jobs and use kill %<n> where you replace n by the number of your ping job.






      share|improve this answer













      If it is your one and only background job you can kill it with kill %1. If not sure you can list all your background jobs with jobs and use kill %<n> where you replace n by the number of your ping job.







      share|improve this answer












      share|improve this answer



      share|improve this answer










      answered yesterday









      mucluxmuclux

      3,22111130




      3,22111130








      • 3





        Also, I found out that n matches the number that is print out in square brackets when running the command.

        – Vineet
        yesterday














      • 3





        Also, I found out that n matches the number that is print out in square brackets when running the command.

        – Vineet
        yesterday








      3




      3





      Also, I found out that n matches the number that is print out in square brackets when running the command.

      – Vineet
      yesterday





      Also, I found out that n matches the number that is print out in square brackets when running the command.

      – Vineet
      yesterday











      3














      Launch a new tab of terminal, run:



      $ pgrep ping
      2564


      Then kill the pid using kill command:



      $ kill 2564





      share|improve this answer
























      • I used kill in the same terminal too (though the output made it difficult to use). However, I was wondering what to do if I couldn't go far back up in the terminal to see the process id printed, so pgrep has helped, additionally.

        – Vineet
        yesterday






      • 2





        When you use pgrep to search processes by name, you can also use pkill to kill them by name. No need to type/copy the process id and use kill.

        – Byte Commander
        yesterday
















      3














      Launch a new tab of terminal, run:



      $ pgrep ping
      2564


      Then kill the pid using kill command:



      $ kill 2564





      share|improve this answer
























      • I used kill in the same terminal too (though the output made it difficult to use). However, I was wondering what to do if I couldn't go far back up in the terminal to see the process id printed, so pgrep has helped, additionally.

        – Vineet
        yesterday






      • 2





        When you use pgrep to search processes by name, you can also use pkill to kill them by name. No need to type/copy the process id and use kill.

        – Byte Commander
        yesterday














      3












      3








      3







      Launch a new tab of terminal, run:



      $ pgrep ping
      2564


      Then kill the pid using kill command:



      $ kill 2564





      share|improve this answer













      Launch a new tab of terminal, run:



      $ pgrep ping
      2564


      Then kill the pid using kill command:



      $ kill 2564






      share|improve this answer












      share|improve this answer



      share|improve this answer










      answered yesterday









      EmmetEmmet

      6,94722245




      6,94722245













      • I used kill in the same terminal too (though the output made it difficult to use). However, I was wondering what to do if I couldn't go far back up in the terminal to see the process id printed, so pgrep has helped, additionally.

        – Vineet
        yesterday






      • 2





        When you use pgrep to search processes by name, you can also use pkill to kill them by name. No need to type/copy the process id and use kill.

        – Byte Commander
        yesterday



















      • I used kill in the same terminal too (though the output made it difficult to use). However, I was wondering what to do if I couldn't go far back up in the terminal to see the process id printed, so pgrep has helped, additionally.

        – Vineet
        yesterday






      • 2





        When you use pgrep to search processes by name, you can also use pkill to kill them by name. No need to type/copy the process id and use kill.

        – Byte Commander
        yesterday

















      I used kill in the same terminal too (though the output made it difficult to use). However, I was wondering what to do if I couldn't go far back up in the terminal to see the process id printed, so pgrep has helped, additionally.

      – Vineet
      yesterday





      I used kill in the same terminal too (though the output made it difficult to use). However, I was wondering what to do if I couldn't go far back up in the terminal to see the process id printed, so pgrep has helped, additionally.

      – Vineet
      yesterday




      2




      2





      When you use pgrep to search processes by name, you can also use pkill to kill them by name. No need to type/copy the process id and use kill.

      – Byte Commander
      yesterday





      When you use pgrep to search processes by name, you can also use pkill to kill them by name. No need to type/copy the process id and use kill.

      – Byte Commander
      yesterday











      3














      When you send a process to the background, whether by using ctrl-z or by & at the end of the command, you get an output in the following format: [index] process-id. If you send multiple processes to the background, the index will keep incrementing every time.



      For example:



      $ sleep 100 &
      [1] 41608
      $ sleep 101 &
      [2] 41609
      $ sleep 102 &
      [3] 41610
      $ sleep 103 &
      [4] 41611
      $ sleep 104 &
      [5] 41612
      $ sleep 105 &
      [6] 41613
      $ sleep 106 &
      [7] 41614


      In order to stop a specific one, you can either use kill <process-id> or use fg <index> followed by ctrl-c



      Example using the previous output:



      $ kill 41614


      or



      $ fg 7
      sleep 106
      ^C





      share|improve this answer




























        3














        When you send a process to the background, whether by using ctrl-z or by & at the end of the command, you get an output in the following format: [index] process-id. If you send multiple processes to the background, the index will keep incrementing every time.



        For example:



        $ sleep 100 &
        [1] 41608
        $ sleep 101 &
        [2] 41609
        $ sleep 102 &
        [3] 41610
        $ sleep 103 &
        [4] 41611
        $ sleep 104 &
        [5] 41612
        $ sleep 105 &
        [6] 41613
        $ sleep 106 &
        [7] 41614


        In order to stop a specific one, you can either use kill <process-id> or use fg <index> followed by ctrl-c



        Example using the previous output:



        $ kill 41614


        or



        $ fg 7
        sleep 106
        ^C





        share|improve this answer


























          3












          3








          3







          When you send a process to the background, whether by using ctrl-z or by & at the end of the command, you get an output in the following format: [index] process-id. If you send multiple processes to the background, the index will keep incrementing every time.



          For example:



          $ sleep 100 &
          [1] 41608
          $ sleep 101 &
          [2] 41609
          $ sleep 102 &
          [3] 41610
          $ sleep 103 &
          [4] 41611
          $ sleep 104 &
          [5] 41612
          $ sleep 105 &
          [6] 41613
          $ sleep 106 &
          [7] 41614


          In order to stop a specific one, you can either use kill <process-id> or use fg <index> followed by ctrl-c



          Example using the previous output:



          $ kill 41614


          or



          $ fg 7
          sleep 106
          ^C





          share|improve this answer













          When you send a process to the background, whether by using ctrl-z or by & at the end of the command, you get an output in the following format: [index] process-id. If you send multiple processes to the background, the index will keep incrementing every time.



          For example:



          $ sleep 100 &
          [1] 41608
          $ sleep 101 &
          [2] 41609
          $ sleep 102 &
          [3] 41610
          $ sleep 103 &
          [4] 41611
          $ sleep 104 &
          [5] 41612
          $ sleep 105 &
          [6] 41613
          $ sleep 106 &
          [7] 41614


          In order to stop a specific one, you can either use kill <process-id> or use fg <index> followed by ctrl-c



          Example using the previous output:



          $ kill 41614


          or



          $ fg 7
          sleep 106
          ^C






          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered yesterday









          DanDan

          7,14534573




          7,14534573























              0














              When you are root, it's simply killall ping.






              share|improve this answer




























                0














                When you are root, it's simply killall ping.






                share|improve this answer


























                  0












                  0








                  0







                  When you are root, it's simply killall ping.






                  share|improve this answer













                  When you are root, it's simply killall ping.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered 16 hours ago









                  Sim SonSim Son

                  365




                  365






















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










                      draft saved

                      draft discarded


















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













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












                      Vineet 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%2f1125926%2fhow-to-terminate-ping-dest%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

                      Plaza Victoria

                      Puebla de Zaragoza

                      Musa