Reason to use startproc, killproc and checkproc in Sys-V type init scripts in OpenSUSEDisplaying all sysvinit...
Am I overreacting to my team leader's unethical requests?
Ordering a word list
(11 of 11: Meta) What is Pyramid Cult's All-Time Favorite?
How can you evade tax by getting employment income just in equity, then using this equity as collateral to take out loan?
A stranger from Norway wants to have money delivered to me
Why are Gatwick's runways too close together?
If a Contingency spell has been cast on a creature, does the Simulacrum spell transfer the contingent spell to its duplicate?
What does "sardine box" mean?
How does The Fools Guild make its money?
Are there any financial disadvantages to living significantly "below your means"?
Double blind peer review when paper cites author's GitHub repo for code
Can I call myself an assistant professor without a PhD?
show stdout containing n with line breaks
Optimal way to extract "positive part" of a multivariate polynomial
Y2K... in 2019?
Can a one way NS Ticket be used as an OV-Chipkaart for P+R Parking in Amsterdam?
How do Mogwai reproduce?
Which likelihood function is used in linear regression?
Looking for a new job because of relocation - is it okay to tell the real reason?
Is it really ~648.69 km/s delta-v to "land" on the surface of the Sun?
Acceptable to cut steak before searing?
What are the uses and limitations of Persuasion, Insight, and Deception against other PCs?
Are there any differences in causality between linear and logistic regression?
During the Space Shuttle Columbia Disaster of 2003, Why Did The Flight Director Say, "Lock the doors."?
Reason to use startproc, killproc and checkproc in Sys-V type init scripts in OpenSUSE
Displaying all sysvinit init scriptsInstall init scripts manually under Debian WheezyConvert sysvinit/upstart init scripts to runitSysV init scripts to systemd migration in RHEL7Reason for rc<boot_facility> named symbolic links in OpenSUSEConfiguring Debian's opendkim package's init script parameters with both init.d and systemctl scripts being presentUsing cloud-init to modify application properties used by init scriptsCan I use SysV init scripts for systemdOpensuse 15.0 and wi-fi don't workopensuse use rpm install NOKEY problem
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
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
bumped to the homepage by Community♦ 2 hours 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
bumped to the homepage by Community♦ 2 hours 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
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
50226 gold badges77 silver badges151 bronze badges
50226 gold badges77 silver badges151 bronze badges
bumped to the homepage by Community♦ 2 hours 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 hours 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 hours 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.
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%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.
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.
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.
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
4584 silver badges14 bronze badges
4584 silver badges14 bronze badges
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