Trjtdtk

How to simplify this time periods definition interface?

Is honey really a supersaturated solution? Does heating to un-crystalize redissolve it or melt it?

how to draw this figure in latex

Bacteria contamination inside a thermos bottle

Print a physical multiplication table

Draw saving money pig (Piggy Bank)

How to use deus ex machina safely?

If I can solve Sudoku, can I solve the Travelling Salesman Problem (TSP)? If so, how?

Time travel from stationary position?

Have the tides ever turned twice on any open problem?

How could an airship be repaired midflight?

I got the following comment from a reputed math journal. What does it mean?

Is "upgrade" the right word to use in this context?

Credit cards used everywhere in Singapore or Malaysia?

How do I change two letters closest to a string and one letter immediately after a string using Notepad++?

Welcoming 2019 Pi day: How to draw the letter π?

Brexit - No Deal Rejection

Why Choose Less Effective Armour Types?

I am confused as to how the inverse of a certain function is found.

Are ETF trackers fundamentally better than individual stocks?

What Firewall and configuration to use for a the average Ubuntu desktop users?

What is the significance behind "40 days" that often appears in the Bible?

My adviser wants to be the first author

Have researchers managed to "reverse time"? If so, what does that mean for physics?

How to terminate ping &

Why does “metacity --replace” hang my system, but “metacity --replace&” is fine?How to redirect output of jobs in background?Ping for 4 timesTerminal not working. Prompt gone!How do I get back to nano after hitting Ctrl-Z if I have no shell prompt (in Matlab session)Terminal command (ping) makes sound on fail/successxdotool does not terminateHow to send a process to background and foreground?Youtube-dl refuses to run in backgroundHow can I run OpenVPN as root in the background, in a script?

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?

command-line

share|improve this question

edited 23 hours ago

Vineet

asked yesterday

VineetVineet

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.

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  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
  23 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

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

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

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

  
  
  
  

 | 
show 1 more comment

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?

command-line

share|improve this question

edited 23 hours ago

Vineet

asked yesterday

VineetVineet

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.

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  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
  23 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

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

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

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

  
  
  
  

 | 
show 1 more comment

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

edited 23 hours ago

Vineet

asked yesterday

VineetVineet

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.

ping <dest> &

share|improve this question

edited 23 hours ago

Vineet

asked yesterday

VineetVineet

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.

share|improve this question

edited 23 hours ago

Vineet

asked yesterday

VineetVineet

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.

asked yesterday

VineetVineet

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.

asked yesterday

VineetVineet

436

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.

share|improve this answer

edited 19 hours ago

answered yesterday

RavexinaRavexina

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
  21 secs ago
  

  
  
  
  

add a comment | 

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

answered yesterday

mucluxmuclux

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
  

  
  
  
  

add a comment | 

3

Launch a new tab of terminal, run:

$ pgrep ping
 2564

Then kill the pid using kill command:

$ kill 2564

share|improve this answer

answered yesterday

EmmetEmmet

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
  

  
  
  
  

add a comment | 

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

answered yesterday

DanDan

7,14534573

add a comment | 

0

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

share|improve this answer

answered 4 hours ago

Sim SonSim Son

365

add a comment | 

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

Sign up or log in

StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

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

Name

Email

Required, but never shown

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.

share|improve this answer

edited 19 hours ago

answered yesterday

RavexinaRavexina

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
  21 secs ago
  

  
  
  
  

add a comment | 

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.

share|improve this answer

edited 19 hours ago

answered yesterday

RavexinaRavexina

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
  21 secs ago
  

  
  
  
  

add a comment | 

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.

share|improve this answer

edited 19 hours ago

answered yesterday

RavexinaRavexina

32.9k1487114

share|improve this answer

edited 19 hours ago

answered yesterday

RavexinaRavexina

32.9k1487114

answered yesterday

RavexinaRavexina

32.9k1487114

answered yesterday

RavexinaRavexina

32.9k1487114

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

answered yesterday

mucluxmuclux

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
  

  
  
  
  

add a comment | 

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

answered yesterday

mucluxmuclux

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
  

  
  
  
  

add a comment | 

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

answered yesterday

mucluxmuclux

3,22111130

share|improve this answer

answered yesterday

mucluxmuclux

3,22111130

answered yesterday

mucluxmuclux

3,22111130

answered yesterday

mucluxmuclux

3,22111130

3

Launch a new tab of terminal, run:

$ pgrep ping
 2564

Then kill the pid using kill command:

$ kill 2564

share|improve this answer

answered yesterday

EmmetEmmet

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
  

  
  
  
  

add a comment | 

3

Launch a new tab of terminal, run:

$ pgrep ping
 2564

Then kill the pid using kill command:

$ kill 2564

share|improve this answer

answered yesterday

EmmetEmmet

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
  

  
  
  
  

add a comment | 

Launch a new tab of terminal, run:

$ pgrep ping
 2564

Then kill the pid using kill command:

$ kill 2564

share|improve this answer

answered yesterday

EmmetEmmet

6,94722245

$ pgrep ping
 2564

$ kill 2564

share|improve this answer

answered yesterday

EmmetEmmet

6,94722245

answered yesterday

EmmetEmmet

6,94722245

answered yesterday

EmmetEmmet

6,94722245

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

answered yesterday

DanDan

7,14534573

add a comment | 

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

answered yesterday

DanDan

7,14534573

add a comment | 

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

answered yesterday

DanDan

7,14534573

$ 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

$ kill 41614

$ fg 7
sleep 106
^C

share|improve this answer

answered yesterday

DanDan

7,14534573

answered yesterday

DanDan

7,14534573

answered yesterday

DanDan

7,14534573

0

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

share|improve this answer

answered 4 hours ago

Sim SonSim Son

365

add a comment | 

0

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

share|improve this answer

answered 4 hours ago

Sim SonSim Son

365

add a comment | 

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

share|improve this answer

answered 4 hours ago

Sim SonSim Son

365

share|improve this answer

answered 4 hours ago

Sim SonSim Son

365

answered 4 hours ago

Sim SonSim Son

365

answered 4 hours ago

Sim SonSim Son

365