Ggthjy

When quoting, must I also copy hyphens used to divide words that continue on the next line?

Is there a single word describing earning money through any means?

Delete database accidentally by a bash, rescue please

Is '大勢の人' redundant?

Why does the Sun have different day lengths, but not the gas giants?

A social experiment. What is the worst that can happen?

why `nmap 192.168.1.97` returns less services than `nmap 127.0.0.1`?

Create all possible words using a set or letters

When were female captains banned from Starfleet?

Will the technology I first learn determine the direction of my future career?

Freedom of speech and where it applies

THT: What is a squared annular “ring”?

Has Darkwing Duck ever met Scrooge McDuck?

Is there an efficient solution to the travelling salesman problem with binary edge weights?

Perfect Cadence in minor key

Is XSS in canonical link possible?

Should I stop contributing to retirement accounts?

How do ground effect vehicles perform turns?

Is a file system driver implemented using a kernel module in Linux?

How much character growth crosses the line into breaking the character

How should I respond when I lied about my education and the company finds out through background check?

getting the weights of intermediate layer in keras

Global amount of publications over time

Difference between -| and |- in TikZ

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

1

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 Mar 15 at 18:45

Vineet

asked Mar 15 at 14:13

VineetVineet

467

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  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
  Mar 15 at 18:07
  
  
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  @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
  Mar 15 at 18:20
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Nitpick: It's not a URL.
  
  – Roger Lipscombe
  Mar 15 at 18:43
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @RogerLipscombe What do you call it, other than destination? Host is a little unsure, considering that a single computer may host many domains
  
  – Vineet
  Mar 15 at 18:48
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  It's a hostname (or an IP address). "a single computer may host many domains" -- not relevant to ping.
  
  – Roger Lipscombe
  Mar 15 at 19:14
  

  
  
  
  

 | 
show 1 more comment

8

1

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 Mar 15 at 18:45

Vineet

asked Mar 15 at 14:13

VineetVineet

467

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  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
  Mar 15 at 18:07
  
  
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  @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
  Mar 15 at 18:20
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Nitpick: It's not a URL.
  
  – Roger Lipscombe
  Mar 15 at 18:43
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @RogerLipscombe What do you call it, other than destination? Host is a little unsure, considering that a single computer may host many domains
  
  – Vineet
  Mar 15 at 18:48
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  It's a hostname (or an IP address). "a single computer may host many domains" -- not relevant to ping.
  
  – Roger Lipscombe
  Mar 15 at 19:14
  

  
  
  
  

 | 
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 Mar 15 at 18:45

Vineet

asked Mar 15 at 14:13

VineetVineet

467

ping <dest> &

share|improve this question

edited Mar 15 at 18:45

Vineet

asked Mar 15 at 14:13

VineetVineet

467

share|improve this question

edited Mar 15 at 18:45

Vineet

asked Mar 15 at 14:13

VineetVineet

467

asked Mar 15 at 14:13

VineetVineet

467

asked Mar 15 at 14:13

VineetVineet

467

6 Answers
6

active

oldest

votes

20

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 Mar 15 at 23:02

answered Mar 15 at 14:17

RavexinaRavexina

33.2k1488116

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  This works. I also realized that fg works if we have multiple background processes, by calling them to the foreground one by one.
  
  – Vineet
  Mar 15 at 14:22
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Yep, that's how it works, you can use jobs to get a list of process that are running in background.
  
  – Ravexina
  Mar 15 at 14:23
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  How did you make that image loop?
  
  – phillipsk
  Mar 16 at 18:25
  

  
  
  
  


• 
  
  
  

  
  3
  

  
  
  
  
  
  

  
  
  @phillipsk It's GIF, that's how GIF works ...
  
  – Ravexina
  Mar 16 at 18:31
  

  
  
  
  

add a comment | 

12

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 Mar 15 at 14:25

mucluxmuclux

3,27111130

• 
  
  
  

  
  4
  

  
  
  
  
  
  

  
  
  Also, I found out that n matches the number that is print out in square brackets when running the command.
  
  – Vineet
  Mar 15 at 14:31
  

  
  
  
  

add a comment | 

5

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 Mar 15 at 14:43

DanDan

7,19034573

add a comment | 

4

Launch a new tab of terminal, run:

$ pgrep ping

  2564

Then kill the pid using kill command:

$ kill 2564

share|improve this answer

answered Mar 15 at 14:17

EmmetEmmet

7,18322245

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  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
  Mar 15 at 14:24
  

  
  
  
  


• 
  
  
  

  
  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
  Mar 15 at 14:29
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  This is useful to know, but for this question it's a bit of overkill. :-p
  
  – tudor
  Mar 18 at 1:45
  

  
  
  
  

add a comment | 

0

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

share|improve this answer

answered Mar 16 at 13:33

Sim SonSim Son

365

add a comment | 

0

Slightly different approach towards a continuous ping is to use -c option and enter the number of time you want it to run, that way it will stop itself after the desired count i.e. below ping will stop after 100 pings

ping -c 100 192.168.1.1 &

share|improve this answer

answered Mar 17 at 9:32

IbraheemIbraheem

235

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


}
});

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

20

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 Mar 15 at 23:02

answered Mar 15 at 14:17

RavexinaRavexina

33.2k1488116

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  This works. I also realized that fg works if we have multiple background processes, by calling them to the foreground one by one.
  
  – Vineet
  Mar 15 at 14:22
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Yep, that's how it works, you can use jobs to get a list of process that are running in background.
  
  – Ravexina
  Mar 15 at 14:23
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  How did you make that image loop?
  
  – phillipsk
  Mar 16 at 18:25
  

  
  
  
  


• 
  
  
  

  
  3
  

  
  
  
  
  
  

  
  
  @phillipsk It's GIF, that's how GIF works ...
  
  – Ravexina
  Mar 16 at 18:31
  

  
  
  
  

add a comment | 

20

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 Mar 15 at 23:02

answered Mar 15 at 14:17

RavexinaRavexina

33.2k1488116

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  This works. I also realized that fg works if we have multiple background processes, by calling them to the foreground one by one.
  
  – Vineet
  Mar 15 at 14:22
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Yep, that's how it works, you can use jobs to get a list of process that are running in background.
  
  – Ravexina
  Mar 15 at 14:23
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  How did you make that image loop?
  
  – phillipsk
  Mar 16 at 18:25
  

  
  
  
  


• 
  
  
  

  
  3
  

  
  
  
  
  
  

  
  
  @phillipsk It's GIF, that's how GIF works ...
  
  – Ravexina
  Mar 16 at 18:31
  

  
  
  
  

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 Mar 15 at 23:02

answered Mar 15 at 14:17

RavexinaRavexina

33.2k1488116

share|improve this answer

edited Mar 15 at 23:02

answered Mar 15 at 14:17

RavexinaRavexina

33.2k1488116

answered Mar 15 at 14:17

RavexinaRavexina

33.2k1488116

answered Mar 15 at 14:17

RavexinaRavexina

33.2k1488116

12

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 Mar 15 at 14:25

mucluxmuclux

3,27111130

• 
  
  
  

  
  4
  

  
  
  
  
  
  

  
  
  Also, I found out that n matches the number that is print out in square brackets when running the command.
  
  – Vineet
  Mar 15 at 14:31
  

  
  
  
  

add a comment | 

12

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 Mar 15 at 14:25

mucluxmuclux

3,27111130

• 
  
  
  

  
  4
  

  
  
  
  
  
  

  
  
  Also, I found out that n matches the number that is print out in square brackets when running the command.
  
  – Vineet
  Mar 15 at 14:31
  

  
  
  
  

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 Mar 15 at 14:25

mucluxmuclux

3,27111130

share|improve this answer

answered Mar 15 at 14:25

mucluxmuclux

3,27111130

answered Mar 15 at 14:25

mucluxmuclux

3,27111130

answered Mar 15 at 14:25

mucluxmuclux

3,27111130

5

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 Mar 15 at 14:43

DanDan

7,19034573

add a comment | 

5

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 Mar 15 at 14:43

DanDan

7,19034573

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 Mar 15 at 14:43

DanDan

7,19034573

$ 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 Mar 15 at 14:43

DanDan

7,19034573

answered Mar 15 at 14:43

DanDan

7,19034573

answered Mar 15 at 14:43

DanDan

7,19034573

4

Launch a new tab of terminal, run:

$ pgrep ping

  2564

Then kill the pid using kill command:

$ kill 2564

share|improve this answer

answered Mar 15 at 14:17

EmmetEmmet

7,18322245

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  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
  Mar 15 at 14:24
  

  
  
  
  


• 
  
  
  

  
  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
  Mar 15 at 14:29
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  This is useful to know, but for this question it's a bit of overkill. :-p
  
  – tudor
  Mar 18 at 1:45
  

  
  
  
  

add a comment | 

4

Launch a new tab of terminal, run:

$ pgrep ping

  2564

Then kill the pid using kill command:

$ kill 2564

share|improve this answer

answered Mar 15 at 14:17

EmmetEmmet

7,18322245

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  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
  Mar 15 at 14:24
  

  
  
  
  


• 
  
  
  

  
  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
  Mar 15 at 14:29
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  This is useful to know, but for this question it's a bit of overkill. :-p
  
  – tudor
  Mar 18 at 1:45
  

  
  
  
  

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 Mar 15 at 14:17

EmmetEmmet

7,18322245

$ pgrep ping

  2564

$ kill 2564

share|improve this answer

answered Mar 15 at 14:17

EmmetEmmet

7,18322245

answered Mar 15 at 14:17

EmmetEmmet

7,18322245

answered Mar 15 at 14:17

EmmetEmmet

7,18322245

0

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

share|improve this answer

answered Mar 16 at 13:33

Sim SonSim Son

365

add a comment | 

0

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

share|improve this answer

answered Mar 16 at 13:33

Sim SonSim Son

365

add a comment | 

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

share|improve this answer

answered Mar 16 at 13:33

Sim SonSim Son

365

share|improve this answer

answered Mar 16 at 13:33

Sim SonSim Son

365

answered Mar 16 at 13:33

Sim SonSim Son

365

answered Mar 16 at 13:33

Sim SonSim Son

365

0

Slightly different approach towards a continuous ping is to use -c option and enter the number of time you want it to run, that way it will stop itself after the desired count i.e. below ping will stop after 100 pings

ping -c 100 192.168.1.1 &

share|improve this answer

answered Mar 17 at 9:32

IbraheemIbraheem

235

add a comment | 

0

Slightly different approach towards a continuous ping is to use -c option and enter the number of time you want it to run, that way it will stop itself after the desired count i.e. below ping will stop after 100 pings

ping -c 100 192.168.1.1 &

share|improve this answer

answered Mar 17 at 9:32

IbraheemIbraheem

235

add a comment | 

Slightly different approach towards a continuous ping is to use -c option and enter the number of time you want it to run, that way it will stop itself after the desired count i.e. below ping will stop after 100 pings

ping -c 100 192.168.1.1 &

share|improve this answer

answered Mar 17 at 9:32

IbraheemIbraheem

235

share|improve this answer

answered Mar 17 at 9:32

IbraheemIbraheem

235

answered Mar 17 at 9:32

IbraheemIbraheem

235

answered Mar 17 at 9:32

IbraheemIbraheem

235