Reason to use startproc, killproc and checkproc in Sys-V type init scripts in OpenSUSE
In OpenSUSE 11.4 sysvinit-tools package contains startproc, killproc and checkproc binaries which according to /etc/init.d/skeleton file and OpenSUSE documentation should be used in Sys-V type of init scripts. What is the idea of those binaries? Couldn't one achieve the same functionality of startproc, killproc and checkproc with nice, sudo, sleep and other similar tools?
opensuse sysvinit
asked Dec 8 '15 at 13:12
MartinMartin
4142571140
bumped to the homepage by Community♦ 2 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
In OpenSUSE 11.4 sysvinit-tools package contains startproc, killproc and checkproc binaries which according to /etc/init.d/skeleton file and OpenSUSE documentation should be used in Sys-V type of init scripts. What is the idea of those binaries? Couldn't one achieve the same functionality of startproc, killproc and checkproc with nice, sudo, sleep and other similar tools?
opensuse sysvinit
asked Dec 8 '15 at 13:12
MartinMartin
4142571140
bumped to the homepage by Community♦ 2 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
In OpenSUSE 11.4 sysvinit-tools package contains startproc, killproc and checkproc binaries which according to /etc/init.d/skeleton file and OpenSUSE documentation should be used in Sys-V type of init scripts. What is the idea of those binaries? Couldn't one achieve the same functionality of startproc, killproc and checkproc with nice, sudo, sleep and other similar tools?
opensuse sysvinit
asked Dec 8 '15 at 13:12
MartinMartin
4142571140
In OpenSUSE 11.4 sysvinit-tools package contains startproc, killproc and checkproc binaries which according to /etc/init.d/skeleton file and OpenSUSE documentation should be used in Sys-V type of init scripts. What is the idea of those binaries? Couldn't one achieve the same functionality of startproc, killproc and checkproc with nice, sudo, sleep and other similar tools?
opensuse sysvinit
opensuse sysvinit
asked Dec 8 '15 at 13:12
MartinMartin
4142571140
asked Dec 8 '15 at 13:12
MartinMartin
4142571140
asked Dec 8 '15 at 13:12
MartinMartin
4142571140
asked Dec 8 '15 at 13:12
MartinMartin
4142571140
asked Dec 8 '15 at 13:12
MartinMartin
4142571140
4142571140
bumped to the homepage by Community♦ 2 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 2 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Let's first define the specific programs:
startproc
startproc: startproc and the LSB variant start_daemon check for all processes of the specified executable and starts it if no processes are found. startproc does not use the pid to search for a process but the full path of the corresponding program which is used to identify the executable
killproc
killproc sends signals to all processes that use the specified executable. If no signal name is specified, the signal SIGTERM is sent. killproc does not use the pid to send a signal to a process but the full path of the corresponding program which is used to identify the executable
checkproc
checkproc checks for running processes that use the specified executable. checkproc does not use the pid to verify a process but the full path of the corresponding program which is used to identify the executable.
nice, sudo, sleep do nothing related to the above programs.
Off course you could do the same logic from kill/start/checkproc in any scripting language (bash for ex.) or other compiled language. But the purpose of those programs is to offer this functionality to all users that need it, so they don't have to bother to write/rewrite the same logic on different distributions and different OSs.
answered Dec 18 '15 at 13:52
cristicristi
448414
add a comment |
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%2f248103%2freason-to-use-startproc-killproc-and-checkproc-in-sys-v-type-init-scripts-in-op%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
Let's first define the specific programs:
startproc
startproc: startproc and the LSB variant start_daemon check for all processes of the specified executable and starts it if no processes are found. startproc does not use the pid to search for a process but the full path of the corresponding program which is used to identify the executable
killproc
killproc sends signals to all processes that use the specified executable. If no signal name is specified, the signal SIGTERM is sent. killproc does not use the pid to send a signal to a process but the full path of the corresponding program which is used to identify the executable
checkproc
checkproc checks for running processes that use the specified executable. checkproc does not use the pid to verify a process but the full path of the corresponding program which is used to identify the executable.
nice, sudo, sleep do nothing related to the above programs.
Off course you could do the same logic from kill/start/checkproc in any scripting language (bash for ex.) or other compiled language. But the purpose of those programs is to offer this functionality to all users that need it, so they don't have to bother to write/rewrite the same logic on different distributions and different OSs.
answered Dec 18 '15 at 13:52
cristicristi
448414
add a comment |
Let's first define the specific programs:
startproc
startproc: startproc and the LSB variant start_daemon check for all processes of the specified executable and starts it if no processes are found. startproc does not use the pid to search for a process but the full path of the corresponding program which is used to identify the executable
killproc
killproc sends signals to all processes that use the specified executable. If no signal name is specified, the signal SIGTERM is sent. killproc does not use the pid to send a signal to a process but the full path of the corresponding program which is used to identify the executable
checkproc
checkproc checks for running processes that use the specified executable. checkproc does not use the pid to verify a process but the full path of the corresponding program which is used to identify the executable.
nice, sudo, sleep do nothing related to the above programs.
Off course you could do the same logic from kill/start/checkproc in any scripting language (bash for ex.) or other compiled language. But the purpose of those programs is to offer this functionality to all users that need it, so they don't have to bother to write/rewrite the same logic on different distributions and different OSs.
answered Dec 18 '15 at 13:52
cristicristi
448414
add a comment |
Let's first define the specific programs:
startproc
startproc: startproc and the LSB variant start_daemon check for all processes of the specified executable and starts it if no processes are found. startproc does not use the pid to search for a process but the full path of the corresponding program which is used to identify the executable
killproc
killproc sends signals to all processes that use the specified executable. If no signal name is specified, the signal SIGTERM is sent. killproc does not use the pid to send a signal to a process but the full path of the corresponding program which is used to identify the executable
checkproc
checkproc checks for running processes that use the specified executable. checkproc does not use the pid to verify a process but the full path of the corresponding program which is used to identify the executable.
nice, sudo, sleep do nothing related to the above programs.
Off course you could do the same logic from kill/start/checkproc in any scripting language (bash for ex.) or other compiled language. But the purpose of those programs is to offer this functionality to all users that need it, so they don't have to bother to write/rewrite the same logic on different distributions and different OSs.
answered Dec 18 '15 at 13:52
cristicristi
448414
Let's first define the specific programs:
startproc
startproc: startproc and the LSB variant start_daemon check for all processes of the specified executable and starts it if no processes are found. startproc does not use the pid to search for a process but the full path of the corresponding program which is used to identify the executable
killproc
killproc sends signals to all processes that use the specified executable. If no signal name is specified, the signal SIGTERM is sent. killproc does not use the pid to send a signal to a process but the full path of the corresponding program which is used to identify the executable
checkproc
checkproc checks for running processes that use the specified executable. checkproc does not use the pid to verify a process but the full path of the corresponding program which is used to identify the executable.
nice, sudo, sleep do nothing related to the above programs.
Off course you could do the same logic from kill/start/checkproc in any scripting language (bash for ex.) or other compiled language. But the purpose of those programs is to offer this functionality to all users that need it, so they don't have to bother to write/rewrite the same logic on different distributions and different OSs.
answered Dec 18 '15 at 13:52
cristicristi
448414
answered Dec 18 '15 at 13:52
cristicristi
448414
answered Dec 18 '15 at 13:52
cristicristi
448414
answered Dec 18 '15 at 13:52
cristicristi
448414
448414
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%2f248103%2freason-to-use-startproc-killproc-and-checkproc-in-sys-v-type-init-scripts-in-op%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
