Mixing
Kill second instance of a process
I'm running two instances of omxiv (Omx Image Viewer). The first instance acts like a background image, and the second instance acts as a slideshow. My question is how can I specifically kill the second instance?
Small note: The second instance will always be opened after the first instance.
I was thinking about killing it by pid, but I am not sure if it will have the same pid after the reboot, therefore this might not work.
Right now I am calling:
pkill -9 omxiv
which is terminating both instances.
debian ubuntu process raspbian
asked Jan 13 at 11:22
DinoDino
1183
add a comment |
I'm running two instances of omxiv (Omx Image Viewer). The first instance acts like a background image, and the second instance acts as a slideshow. My question is how can I specifically kill the second instance?
Small note: The second instance will always be opened after the first instance.
I was thinking about killing it by pid, but I am not sure if it will have the same pid after the reboot, therefore this might not work.
Right now I am calling:
pkill -9 omxiv
which is terminating both instances.
debian ubuntu process raspbian
asked Jan 13 at 11:22
DinoDino
1183
add a comment |
I'm running two instances of omxiv (Omx Image Viewer). The first instance acts like a background image, and the second instance acts as a slideshow. My question is how can I specifically kill the second instance?
Small note: The second instance will always be opened after the first instance.
I was thinking about killing it by pid, but I am not sure if it will have the same pid after the reboot, therefore this might not work.
Right now I am calling:
pkill -9 omxiv
which is terminating both instances.
debian ubuntu process raspbian
asked Jan 13 at 11:22
DinoDino
1183
I'm running two instances of omxiv (Omx Image Viewer). The first instance acts like a background image, and the second instance acts as a slideshow. My question is how can I specifically kill the second instance?
Small note: The second instance will always be opened after the first instance.
I was thinking about killing it by pid, but I am not sure if it will have the same pid after the reboot, therefore this might not work.
Right now I am calling:
pkill -9 omxiv
which is terminating both instances.
debian ubuntu process raspbian
debian ubuntu process raspbian
asked Jan 13 at 11:22
DinoDino
1183
asked Jan 13 at 11:22
DinoDino
1183
asked Jan 13 at 11:22
DinoDino
1183
asked Jan 13 at 11:22
DinoDino
1183
asked Jan 13 at 11:22
DinoDino
1183
1183
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
pkill has a -n flag that will make it only affect the most recently started ("newest") matching process.
pkill -n omxiv
If the omxiv process is well behaved, there is no need to use -9.
There is also a -o flag that will make pkill send a signal to the oldest matching process.
Note that using pkill -n will always kill the newest instance. If you have three processes, it will kill the third, not the second (as per title of question).
answered Jan 13 at 11:27
KusalanandaKusalananda
129k16245404
That's exactly what I needed, it works great. Thanks for explanation
– Dino
Jan 13 at 11:30
According to the man page, this also works on Debian and Ubuntu.
– kasperd
Jan 13 at 19:52
1
@kasperd I was a bit careful, because OpenBSDpkillhas some options not implemented on Linux systems, for example-qto be quiet.
– Kusalananda
Jan 13 at 20:29
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%2f494235%2fkill-second-instance-of-a-process%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
pkill has a -n flag that will make it only affect the most recently started ("newest") matching process.
pkill -n omxiv
If the omxiv process is well behaved, there is no need to use -9.
There is also a -o flag that will make pkill send a signal to the oldest matching process.
Note that using pkill -n will always kill the newest instance. If you have three processes, it will kill the third, not the second (as per title of question).
answered Jan 13 at 11:27
KusalanandaKusalananda
129k16245404
That's exactly what I needed, it works great. Thanks for explanation
– Dino
Jan 13 at 11:30
According to the man page, this also works on Debian and Ubuntu.
– kasperd
Jan 13 at 19:52
1
@kasperd I was a bit careful, because OpenBSDpkillhas some options not implemented on Linux systems, for example-qto be quiet.
– Kusalananda
Jan 13 at 20:29
add a comment |
pkill has a -n flag that will make it only affect the most recently started ("newest") matching process.
pkill -n omxiv
If the omxiv process is well behaved, there is no need to use -9.
There is also a -o flag that will make pkill send a signal to the oldest matching process.
Note that using pkill -n will always kill the newest instance. If you have three processes, it will kill the third, not the second (as per title of question).
answered Jan 13 at 11:27
KusalanandaKusalananda
129k16245404
That's exactly what I needed, it works great. Thanks for explanation
– Dino
Jan 13 at 11:30
According to the man page, this also works on Debian and Ubuntu.
– kasperd
Jan 13 at 19:52
1
@kasperd I was a bit careful, because OpenBSDpkillhas some options not implemented on Linux systems, for example-qto be quiet.
– Kusalananda
Jan 13 at 20:29
add a comment |
pkill has a -n flag that will make it only affect the most recently started ("newest") matching process.
pkill -n omxiv
If the omxiv process is well behaved, there is no need to use -9.
There is also a -o flag that will make pkill send a signal to the oldest matching process.
Note that using pkill -n will always kill the newest instance. If you have three processes, it will kill the third, not the second (as per title of question).
answered Jan 13 at 11:27
KusalanandaKusalananda
129k16245404
pkill has a -n flag that will make it only affect the most recently started ("newest") matching process.
pkill -n omxiv
If the omxiv process is well behaved, there is no need to use -9.
There is also a -o flag that will make pkill send a signal to the oldest matching process.
Note that using pkill -n will always kill the newest instance. If you have three processes, it will kill the third, not the second (as per title of question).
answered Jan 13 at 11:27
KusalanandaKusalananda
129k16245404
edited Jan 13 at 20:29
answered Jan 13 at 11:27
KusalanandaKusalananda
129k16245404
answered Jan 13 at 11:27
KusalanandaKusalananda
129k16245404
answered Jan 13 at 11:27
KusalanandaKusalananda
129k16245404
129k16245404
That's exactly what I needed, it works great. Thanks for explanation
– Dino
Jan 13 at 11:30
According to the man page, this also works on Debian and Ubuntu.
– kasperd
Jan 13 at 19:52
1
@kasperd I was a bit careful, because OpenBSDpkillhas some options not implemented on Linux systems, for example-qto be quiet.
– Kusalananda
Jan 13 at 20:29
add a comment |
That's exactly what I needed, it works great. Thanks for explanation
– Dino
Jan 13 at 11:30
According to the man page, this also works on Debian and Ubuntu.
– kasperd
Jan 13 at 19:52
1
@kasperd I was a bit careful, because OpenBSDpkillhas some options not implemented on Linux systems, for example-qto be quiet.
– Kusalananda
Jan 13 at 20:29
That's exactly what I needed, it works great. Thanks for explanation
– Dino
Jan 13 at 11:30
That's exactly what I needed, it works great. Thanks for explanation
– Dino
Jan 13 at 11:30
According to the man page, this also works on Debian and Ubuntu.
– kasperd
Jan 13 at 19:52
According to the man page, this also works on Debian and Ubuntu.
– kasperd
Jan 13 at 19:52
1
1
@kasperd I was a bit careful, because OpenBSD
pkill has some options not implemented on Linux systems, for example -q to be quiet.– Kusalananda
Jan 13 at 20:29
@kasperd I was a bit careful, because OpenBSD
pkill has some options not implemented on Linux systems, for example -q to be quiet.– Kusalananda
Jan 13 at 20:29
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%2f494235%2fkill-second-instance-of-a-process%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
