If you put something in the background does this mean it may also ignore interrpts?
I know that you can kill the process by job ID or PID using PS or KIll. but if its in the background using '&' will sending an interrupt signal will it also kill that process or Job?
terminal background-process signals
add a comment |
I know that you can kill the process by job ID or PID using PS or KIll. but if its in the background using '&' will sending an interrupt signal will it also kill that process or Job?
terminal background-process signals
add a comment |
I know that you can kill the process by job ID or PID using PS or KIll. but if its in the background using '&' will sending an interrupt signal will it also kill that process or Job?
terminal background-process signals
I know that you can kill the process by job ID or PID using PS or KIll. but if its in the background using '&' will sending an interrupt signal will it also kill that process or Job?
terminal background-process signals
terminal background-process signals
edited Dec 19 '18 at 23:59
Rui F Ribeiro
39k1479130
39k1479130
asked Jan 4 '18 at 4:16
gabru678
1
1
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
it the background just means the shell it not waiting for it to finish,
it can still still receive signals, (such as SIGINT
), use the kill
command to send signals.
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%2f414699%2fif-you-put-something-in-the-background-does-this-mean-it-may-also-ignore-interrp%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
it the background just means the shell it not waiting for it to finish,
it can still still receive signals, (such as SIGINT
), use the kill
command to send signals.
add a comment |
it the background just means the shell it not waiting for it to finish,
it can still still receive signals, (such as SIGINT
), use the kill
command to send signals.
add a comment |
it the background just means the shell it not waiting for it to finish,
it can still still receive signals, (such as SIGINT
), use the kill
command to send signals.
it the background just means the shell it not waiting for it to finish,
it can still still receive signals, (such as SIGINT
), use the kill
command to send signals.
answered Jan 4 '18 at 4:45
Jasen
2,106713
2,106713
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.
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.
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%2f414699%2fif-you-put-something-in-the-background-does-this-mean-it-may-also-ignore-interrp%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