Difference between stop, kill and terminate in Xfce task manager 1.0.1
I'm on Xfce desktop environment, using "Task manager 1.0.1".
For more precision you can found it here, a link I got in the "About".
When secondary clicking a process, I can stop it, kill it or terminate it. I need to know a precise definition of each of those terms for this application.
xfce kill
edited Feb 15 at 5:37
Rui F Ribeiro
40.7k1479137
asked Feb 8 '16 at 1:46
SantropedroSantropedro
17712
add a comment |
I'm on Xfce desktop environment, using "Task manager 1.0.1".
For more precision you can found it here, a link I got in the "About".
When secondary clicking a process, I can stop it, kill it or terminate it. I need to know a precise definition of each of those terms for this application.
xfce kill
edited Feb 15 at 5:37
Rui F Ribeiro
40.7k1479137
asked Feb 8 '16 at 1:46
SantropedroSantropedro
17712
add a comment |
I'm on Xfce desktop environment, using "Task manager 1.0.1".
For more precision you can found it here, a link I got in the "About".
When secondary clicking a process, I can stop it, kill it or terminate it. I need to know a precise definition of each of those terms for this application.
xfce kill
edited Feb 15 at 5:37
Rui F Ribeiro
40.7k1479137
asked Feb 8 '16 at 1:46
SantropedroSantropedro
17712
I'm on Xfce desktop environment, using "Task manager 1.0.1".
For more precision you can found it here, a link I got in the "About".
When secondary clicking a process, I can stop it, kill it or terminate it. I need to know a precise definition of each of those terms for this application.
xfce kill
xfce kill
edited Feb 15 at 5:37
Rui F Ribeiro
40.7k1479137
asked Feb 8 '16 at 1:46
SantropedroSantropedro
17712
edited Feb 15 at 5:37
Rui F Ribeiro
40.7k1479137
asked Feb 8 '16 at 1:46
SantropedroSantropedro
17712
edited Feb 15 at 5:37
Rui F Ribeiro
40.7k1479137
edited Feb 15 at 5:37
Rui F Ribeiro
40.7k1479137
edited Feb 15 at 5:37
Rui F Ribeiro
40.7k1479137
40.7k1479137
asked Feb 8 '16 at 1:46
SantropedroSantropedro
17712
asked Feb 8 '16 at 1:46
SantropedroSantropedro
17712
asked Feb 8 '16 at 1:46
SantropedroSantropedro
17712
17712
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
Use the source:
switch (xtm_signal)
{
case XTM_SIGNAL_TERMINATE:
sig = SIGTERM;
break;
case XTM_SIGNAL_STOP:
sig = SIGSTOP;
break;
case XTM_SIGNAL_CONTINUE:
sig = SIGCONT;
break;
case XTM_SIGNAL_KILL:
sig = SIGKILL;
break;
default:
return TRUE;
}
You can see that the task manager sends corresponding SIGSTOP (like a controlZ), SIGTERM (like controlC) and SIGKILL (like kill -9).
Further reading:
- kill - terminate a process
- kill - send a signal to a process
answered Feb 8 '16 at 2:07
Thomas DickeyThomas Dickey
53.7k5102175
Ctrl-c usually sends a SIGINT, not a SIGTERM.
– RealSkeptic
Feb 8 '16 at 15:39
This is useful to me because I've never thought of reading the code until now even if that's the reason I switched to Linux. What can I study, if I have free time, to understand better Linux source code (not the kernel, that seems complicated)?
– Santropedro
Feb 8 '16 at 15:44
add a comment |
It sends different stop signals to a process. Here's some info:
Stop: SIGSTOP - This signal makes the operating system pause a process's execution. The process cannot ignore the signal.
Kill: SIGKILL - The SIGKILL signal forces the process to stop executing immediately. The program cannot ignore this signal. This process does not get to clean-up either.
Terminate: SIGTERM - This signal requests a process to stop running. This signal can be ignored. The process is given time to gracefully shutdown. When a program gracefully shuts down, that means it is given time to save its progress and release resources. In other words, it is not forced to stop. SIGINT is very similar to SIGTERM.
answered Feb 8 '16 at 2:07
GeneGene
1,2451820
add a comment |
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
});
}
});
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f260675%2fdifference-between-stop-kill-and-terminate-in-xfce-task-manager-1-0-1%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Use the source:
switch (xtm_signal)
{
case XTM_SIGNAL_TERMINATE:
sig = SIGTERM;
break;
case XTM_SIGNAL_STOP:
sig = SIGSTOP;
break;
case XTM_SIGNAL_CONTINUE:
sig = SIGCONT;
break;
case XTM_SIGNAL_KILL:
sig = SIGKILL;
break;
default:
return TRUE;
}
You can see that the task manager sends corresponding SIGSTOP (like a controlZ), SIGTERM (like controlC) and SIGKILL (like kill -9).
Further reading:
- kill - terminate a process
- kill - send a signal to a process
answered Feb 8 '16 at 2:07
Thomas DickeyThomas Dickey
53.7k5102175
Ctrl-c usually sends a SIGINT, not a SIGTERM.
– RealSkeptic
Feb 8 '16 at 15:39
This is useful to me because I've never thought of reading the code until now even if that's the reason I switched to Linux. What can I study, if I have free time, to understand better Linux source code (not the kernel, that seems complicated)?
– Santropedro
Feb 8 '16 at 15:44
add a comment |
Use the source:
switch (xtm_signal)
{
case XTM_SIGNAL_TERMINATE:
sig = SIGTERM;
break;
case XTM_SIGNAL_STOP:
sig = SIGSTOP;
break;
case XTM_SIGNAL_CONTINUE:
sig = SIGCONT;
break;
case XTM_SIGNAL_KILL:
sig = SIGKILL;
break;
default:
return TRUE;
}
You can see that the task manager sends corresponding SIGSTOP (like a controlZ), SIGTERM (like controlC) and SIGKILL (like kill -9).
Further reading:
- kill - terminate a process
- kill - send a signal to a process
answered Feb 8 '16 at 2:07
Thomas DickeyThomas Dickey
53.7k5102175
Ctrl-c usually sends a SIGINT, not a SIGTERM.
– RealSkeptic
Feb 8 '16 at 15:39
This is useful to me because I've never thought of reading the code until now even if that's the reason I switched to Linux. What can I study, if I have free time, to understand better Linux source code (not the kernel, that seems complicated)?
– Santropedro
Feb 8 '16 at 15:44
add a comment |
Use the source:
switch (xtm_signal)
{
case XTM_SIGNAL_TERMINATE:
sig = SIGTERM;
break;
case XTM_SIGNAL_STOP:
sig = SIGSTOP;
break;
case XTM_SIGNAL_CONTINUE:
sig = SIGCONT;
break;
case XTM_SIGNAL_KILL:
sig = SIGKILL;
break;
default:
return TRUE;
}
You can see that the task manager sends corresponding SIGSTOP (like a controlZ), SIGTERM (like controlC) and SIGKILL (like kill -9).
Further reading:
- kill - terminate a process
- kill - send a signal to a process
answered Feb 8 '16 at 2:07
Thomas DickeyThomas Dickey
53.7k5102175
Use the source:
switch (xtm_signal)
{
case XTM_SIGNAL_TERMINATE:
sig = SIGTERM;
break;
case XTM_SIGNAL_STOP:
sig = SIGSTOP;
break;
case XTM_SIGNAL_CONTINUE:
sig = SIGCONT;
break;
case XTM_SIGNAL_KILL:
sig = SIGKILL;
break;
default:
return TRUE;
}
You can see that the task manager sends corresponding SIGSTOP (like a controlZ), SIGTERM (like controlC) and SIGKILL (like kill -9).
Further reading:
- kill - terminate a process
- kill - send a signal to a process
answered Feb 8 '16 at 2:07
Thomas DickeyThomas Dickey
53.7k5102175
answered Feb 8 '16 at 2:07
Thomas DickeyThomas Dickey
53.7k5102175
answered Feb 8 '16 at 2:07
Thomas DickeyThomas Dickey
53.7k5102175
answered Feb 8 '16 at 2:07
Thomas DickeyThomas Dickey
53.7k5102175
53.7k5102175
Ctrl-c usually sends a SIGINT, not a SIGTERM.
– RealSkeptic
Feb 8 '16 at 15:39
This is useful to me because I've never thought of reading the code until now even if that's the reason I switched to Linux. What can I study, if I have free time, to understand better Linux source code (not the kernel, that seems complicated)?
– Santropedro
Feb 8 '16 at 15:44
add a comment |
Ctrl-c usually sends a SIGINT, not a SIGTERM.
– RealSkeptic
Feb 8 '16 at 15:39
This is useful to me because I've never thought of reading the code until now even if that's the reason I switched to Linux. What can I study, if I have free time, to understand better Linux source code (not the kernel, that seems complicated)?
– Santropedro
Feb 8 '16 at 15:44
Ctrl-c usually sends a SIGINT, not a SIGTERM.
– RealSkeptic
Feb 8 '16 at 15:39
Ctrl-c usually sends a SIGINT, not a SIGTERM.
– RealSkeptic
Feb 8 '16 at 15:39
This is useful to me because I've never thought of reading the code until now even if that's the reason I switched to Linux. What can I study, if I have free time, to understand better Linux source code (not the kernel, that seems complicated)?
– Santropedro
Feb 8 '16 at 15:44
This is useful to me because I've never thought of reading the code until now even if that's the reason I switched to Linux. What can I study, if I have free time, to understand better Linux source code (not the kernel, that seems complicated)?
– Santropedro
Feb 8 '16 at 15:44
add a comment |
It sends different stop signals to a process. Here's some info:
Stop: SIGSTOP - This signal makes the operating system pause a process's execution. The process cannot ignore the signal.
Kill: SIGKILL - The SIGKILL signal forces the process to stop executing immediately. The program cannot ignore this signal. This process does not get to clean-up either.
Terminate: SIGTERM - This signal requests a process to stop running. This signal can be ignored. The process is given time to gracefully shutdown. When a program gracefully shuts down, that means it is given time to save its progress and release resources. In other words, it is not forced to stop. SIGINT is very similar to SIGTERM.
answered Feb 8 '16 at 2:07
GeneGene
1,2451820
add a comment |
It sends different stop signals to a process. Here's some info:
Stop: SIGSTOP - This signal makes the operating system pause a process's execution. The process cannot ignore the signal.
Kill: SIGKILL - The SIGKILL signal forces the process to stop executing immediately. The program cannot ignore this signal. This process does not get to clean-up either.
Terminate: SIGTERM - This signal requests a process to stop running. This signal can be ignored. The process is given time to gracefully shutdown. When a program gracefully shuts down, that means it is given time to save its progress and release resources. In other words, it is not forced to stop. SIGINT is very similar to SIGTERM.
answered Feb 8 '16 at 2:07
GeneGene
1,2451820
add a comment |
It sends different stop signals to a process. Here's some info:
Stop: SIGSTOP - This signal makes the operating system pause a process's execution. The process cannot ignore the signal.
Kill: SIGKILL - The SIGKILL signal forces the process to stop executing immediately. The program cannot ignore this signal. This process does not get to clean-up either.
Terminate: SIGTERM - This signal requests a process to stop running. This signal can be ignored. The process is given time to gracefully shutdown. When a program gracefully shuts down, that means it is given time to save its progress and release resources. In other words, it is not forced to stop. SIGINT is very similar to SIGTERM.
answered Feb 8 '16 at 2:07
GeneGene
1,2451820
It sends different stop signals to a process. Here's some info:
Stop: SIGSTOP - This signal makes the operating system pause a process's execution. The process cannot ignore the signal.
Kill: SIGKILL - The SIGKILL signal forces the process to stop executing immediately. The program cannot ignore this signal. This process does not get to clean-up either.
Terminate: SIGTERM - This signal requests a process to stop running. This signal can be ignored. The process is given time to gracefully shutdown. When a program gracefully shuts down, that means it is given time to save its progress and release resources. In other words, it is not forced to stop. SIGINT is very similar to SIGTERM.
answered Feb 8 '16 at 2:07
GeneGene
1,2451820
answered Feb 8 '16 at 2:07
GeneGene
1,2451820
answered Feb 8 '16 at 2:07
GeneGene
1,2451820
answered Feb 8 '16 at 2:07
GeneGene
1,2451820
1,2451820
add a comment |
add a comment |
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.
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f260675%2fdifference-between-stop-kill-and-terminate-in-xfce-task-manager-1-0-1%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
