How to send signals to all processes of my program
I have a program which has a daemon and some other commandline stuff, which all may run simultaneously. I have a condition where I need to kill all of them, but I don't want to parse /proc since that will be so much for think. I'm thinking about setting their Process Group IDs to something I know, but I think it won't work since they should not be in the same session. Is there a way to do this ?
Please don't mind if it sounds dumb to you, any help is appreciated.
linux c++
asked Feb 25 at 5:06
Jaymin SutharJaymin Suthar
61
add a comment |
I have a program which has a daemon and some other commandline stuff, which all may run simultaneously. I have a condition where I need to kill all of them, but I don't want to parse /proc since that will be so much for think. I'm thinking about setting their Process Group IDs to something I know, but I think it won't work since they should not be in the same session. Is there a way to do this ?
Please don't mind if it sounds dumb to you, any help is appreciated.
linux c++
asked Feb 25 at 5:06
Jaymin SutharJaymin Suthar
61
1
Is that 'some other commandline stuff' started by the daemon, or by the user?
– grawity
Feb 25 at 7:40
1
By the user, the daemon received input from them and acts as requested.
– Jaymin Suthar
Feb 25 at 9:28
Isn't that whatkillalldoes?
– Xen2050
Feb 25 at 10:40
What is the reason for killing the commandline client programs? Good design would be to make them exit automatically as soon as connection to the daemon is lost.
– grawity
Feb 25 at 11:55
add a comment |
I have a program which has a daemon and some other commandline stuff, which all may run simultaneously. I have a condition where I need to kill all of them, but I don't want to parse /proc since that will be so much for think. I'm thinking about setting their Process Group IDs to something I know, but I think it won't work since they should not be in the same session. Is there a way to do this ?
Please don't mind if it sounds dumb to you, any help is appreciated.
linux c++
asked Feb 25 at 5:06
Jaymin SutharJaymin Suthar
61
I have a program which has a daemon and some other commandline stuff, which all may run simultaneously. I have a condition where I need to kill all of them, but I don't want to parse /proc since that will be so much for think. I'm thinking about setting their Process Group IDs to something I know, but I think it won't work since they should not be in the same session. Is there a way to do this ?
Please don't mind if it sounds dumb to you, any help is appreciated.
linux c++
linux c++
asked Feb 25 at 5:06
Jaymin SutharJaymin Suthar
61
asked Feb 25 at 5:06
Jaymin SutharJaymin Suthar
61
asked Feb 25 at 5:06
Jaymin SutharJaymin Suthar
61
asked Feb 25 at 5:06
Jaymin SutharJaymin Suthar
61
asked Feb 25 at 5:06
Jaymin SutharJaymin Suthar
61
61
1
Is that 'some other commandline stuff' started by the daemon, or by the user?
– grawity
Feb 25 at 7:40
1
By the user, the daemon received input from them and acts as requested.
– Jaymin Suthar
Feb 25 at 9:28
Isn't that whatkillalldoes?
– Xen2050
Feb 25 at 10:40
What is the reason for killing the commandline client programs? Good design would be to make them exit automatically as soon as connection to the daemon is lost.
– grawity
Feb 25 at 11:55
add a comment |
1
Is that 'some other commandline stuff' started by the daemon, or by the user?
– grawity
Feb 25 at 7:40
1
By the user, the daemon received input from them and acts as requested.
– Jaymin Suthar
Feb 25 at 9:28
Isn't that whatkillalldoes?
– Xen2050
Feb 25 at 10:40
What is the reason for killing the commandline client programs? Good design would be to make them exit automatically as soon as connection to the daemon is lost.
– grawity
Feb 25 at 11:55
1
1
Is that 'some other commandline stuff' started by the daemon, or by the user?
– grawity
Feb 25 at 7:40
Is that 'some other commandline stuff' started by the daemon, or by the user?
– grawity
Feb 25 at 7:40
1
1
By the user, the daemon received input from them and acts as requested.
– Jaymin Suthar
Feb 25 at 9:28
By the user, the daemon received input from them and acts as requested.
– Jaymin Suthar
Feb 25 at 9:28
Isn't that what
killall does?– Xen2050
Feb 25 at 10:40
Isn't that what
killall does?– Xen2050
Feb 25 at 10:40
What is the reason for killing the commandline client programs? Good design would be to make them exit automatically as soon as connection to the daemon is lost.
– grawity
Feb 25 at 11:55
What is the reason for killing the commandline client programs? Good design would be to make them exit automatically as soon as connection to the daemon is lost.
– grawity
Feb 25 at 11:55
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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
});
}
});
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%2fsuperuser.com%2fquestions%2f1409135%2fhow-to-send-signals-to-all-processes-of-my-program%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Super User!
- 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%2fsuperuser.com%2fquestions%2f1409135%2fhow-to-send-signals-to-all-processes-of-my-program%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
1
Is that 'some other commandline stuff' started by the daemon, or by the user?
– grawity
Feb 25 at 7:40
1
By the user, the daemon received input from them and acts as requested.
– Jaymin Suthar
Feb 25 at 9:28
Isn't that what
killalldoes?– Xen2050
Feb 25 at 10:40
What is the reason for killing the commandline client programs? Good design would be to make them exit automatically as soon as connection to the daemon is lost.
– grawity
Feb 25 at 11:55