systemd's [ok] and [fail] at the beginning of the line
I have got to re-write heaps of boot scripts for a variety of servers of mine because of upgrading from CentOS 6.X (SysVinit) to CentOS 7.X (systemd).
There is a file "/etc/rc.d/init.d/function" that contains a number of functions that handle the printout for "[ok]" and "[fail]". There are called "echo_success" and "echo_failure". They are still part of the latest version (compatibility) but they print the [OK] and [fail] at COL 60, not at COL 0.
All other boot up scripts/daemons show the [OK] and [FAIL] at the beginning and then the [UNIT] Description.
How do I achieve this using existing functions that are part of systemd?
Does systemd handle this and I just need to return "fail" and "ok"?
But how?
This is especially tricky if you use "ExecStart" and "ExecStop".
Do I just dump error info to the logs and not print anything but only return "success", "fail" and "warning"?
What are the values of "success", "fail" and "warning"?
thanks
systemd
New contributor
add a comment |
I have got to re-write heaps of boot scripts for a variety of servers of mine because of upgrading from CentOS 6.X (SysVinit) to CentOS 7.X (systemd).
There is a file "/etc/rc.d/init.d/function" that contains a number of functions that handle the printout for "[ok]" and "[fail]". There are called "echo_success" and "echo_failure". They are still part of the latest version (compatibility) but they print the [OK] and [fail] at COL 60, not at COL 0.
All other boot up scripts/daemons show the [OK] and [FAIL] at the beginning and then the [UNIT] Description.
How do I achieve this using existing functions that are part of systemd?
Does systemd handle this and I just need to return "fail" and "ok"?
But how?
This is especially tricky if you use "ExecStart" and "ExecStop".
Do I just dump error info to the logs and not print anything but only return "success", "fail" and "warning"?
What are the values of "success", "fail" and "warning"?
thanks
systemd
New contributor
add a comment |
I have got to re-write heaps of boot scripts for a variety of servers of mine because of upgrading from CentOS 6.X (SysVinit) to CentOS 7.X (systemd).
There is a file "/etc/rc.d/init.d/function" that contains a number of functions that handle the printout for "[ok]" and "[fail]". There are called "echo_success" and "echo_failure". They are still part of the latest version (compatibility) but they print the [OK] and [fail] at COL 60, not at COL 0.
All other boot up scripts/daemons show the [OK] and [FAIL] at the beginning and then the [UNIT] Description.
How do I achieve this using existing functions that are part of systemd?
Does systemd handle this and I just need to return "fail" and "ok"?
But how?
This is especially tricky if you use "ExecStart" and "ExecStop".
Do I just dump error info to the logs and not print anything but only return "success", "fail" and "warning"?
What are the values of "success", "fail" and "warning"?
thanks
systemd
New contributor
I have got to re-write heaps of boot scripts for a variety of servers of mine because of upgrading from CentOS 6.X (SysVinit) to CentOS 7.X (systemd).
There is a file "/etc/rc.d/init.d/function" that contains a number of functions that handle the printout for "[ok]" and "[fail]". There are called "echo_success" and "echo_failure". They are still part of the latest version (compatibility) but they print the [OK] and [fail] at COL 60, not at COL 0.
All other boot up scripts/daemons show the [OK] and [FAIL] at the beginning and then the [UNIT] Description.
How do I achieve this using existing functions that are part of systemd?
Does systemd handle this and I just need to return "fail" and "ok"?
But how?
This is especially tricky if you use "ExecStart" and "ExecStop".
Do I just dump error info to the logs and not print anything but only return "success", "fail" and "warning"?
What are the values of "success", "fail" and "warning"?
thanks
systemd
systemd
New contributor
New contributor
New contributor
asked 7 mins ago
JobstJobst
1011
1011
New contributor
New contributor
add a comment |
add a comment |
0
active
oldest
votes
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
});
}
});
Jobst is a new contributor. Be nice, and check out our Code of Conduct.
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%2f504410%2fsystemds-ok-and-fail-at-the-beginning-of-the-line%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
Jobst is a new contributor. Be nice, and check out our Code of Conduct.
Jobst is a new contributor. Be nice, and check out our Code of Conduct.
Jobst is a new contributor. Be nice, and check out our Code of Conduct.
Jobst is a new contributor. Be nice, and check out our Code of Conduct.
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%2f504410%2fsystemds-ok-and-fail-at-the-beginning-of-the-line%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