How to track all child processes spawned by a systemctl service
I have a system service
[Unit]
Description=dynsock server
After=network.target
[Service]
EnvironmentFile=/etc/dynsock.env
ExecStart=/usr/local/bin/dynctl.sh $SERVER $COUNT $BASEPORT $AUTH
ExecStop=/usr/local/bin/dynsock_onfailure.sh down
Restart=always
Type=forking
[Install]
Alias=dynsock.service
dynctl.sh will start $count child process. I hope when some process dead, systemctl will restart, and exec ExecStop . But system will only restart until all child process dead.
linux ubuntu systemctl
asked Jun 21 '18 at 8:08
jianxi sunjianxi sun
12
add a comment |
I have a system service
[Unit]
Description=dynsock server
After=network.target
[Service]
EnvironmentFile=/etc/dynsock.env
ExecStart=/usr/local/bin/dynctl.sh $SERVER $COUNT $BASEPORT $AUTH
ExecStop=/usr/local/bin/dynsock_onfailure.sh down
Restart=always
Type=forking
[Install]
Alias=dynsock.service
dynctl.sh will start $count child process. I hope when some process dead, systemctl will restart, and exec ExecStop . But system will only restart until all child process dead.
linux ubuntu systemctl
asked Jun 21 '18 at 8:08
jianxi sunjianxi sun
12
add a comment |
I have a system service
[Unit]
Description=dynsock server
After=network.target
[Service]
EnvironmentFile=/etc/dynsock.env
ExecStart=/usr/local/bin/dynctl.sh $SERVER $COUNT $BASEPORT $AUTH
ExecStop=/usr/local/bin/dynsock_onfailure.sh down
Restart=always
Type=forking
[Install]
Alias=dynsock.service
dynctl.sh will start $count child process. I hope when some process dead, systemctl will restart, and exec ExecStop . But system will only restart until all child process dead.
linux ubuntu systemctl
asked Jun 21 '18 at 8:08
jianxi sunjianxi sun
12
I have a system service
[Unit]
Description=dynsock server
After=network.target
[Service]
EnvironmentFile=/etc/dynsock.env
ExecStart=/usr/local/bin/dynctl.sh $SERVER $COUNT $BASEPORT $AUTH
ExecStop=/usr/local/bin/dynsock_onfailure.sh down
Restart=always
Type=forking
[Install]
Alias=dynsock.service
dynctl.sh will start $count child process. I hope when some process dead, systemctl will restart, and exec ExecStop . But system will only restart until all child process dead.
linux ubuntu systemctl
linux ubuntu systemctl
asked Jun 21 '18 at 8:08
jianxi sunjianxi sun
12
asked Jun 21 '18 at 8:08
jianxi sunjianxi sun
12
asked Jun 21 '18 at 8:08
jianxi sunjianxi sun
12
asked Jun 21 '18 at 8:08
jianxi sunjianxi sun
12
asked Jun 21 '18 at 8:08
jianxi sunjianxi sun
12
12
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
systemctl can't possibly know the ways dynctl.sh is forking so that it could know how many child processes must be alive at a given time. That's why you have to manage the life cycle of the processes, so that when one child process is dead, the service will be restarted.
I suggest using the main process as a master for the other ones, so that by using grep or pgrep it could determine if all children processes are alive, and if not it will give the comand systemctl restart <your service>.
Cheers, hope it helps
answered Feb 19 at 10:41
velikiveliki
114
add a comment |
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%2f1333069%2fhow-to-track-all-child-processes-spawned-by-a-systemctl-service%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
systemctl can't possibly know the ways dynctl.sh is forking so that it could know how many child processes must be alive at a given time. That's why you have to manage the life cycle of the processes, so that when one child process is dead, the service will be restarted.
I suggest using the main process as a master for the other ones, so that by using grep or pgrep it could determine if all children processes are alive, and if not it will give the comand systemctl restart <your service>.
Cheers, hope it helps
answered Feb 19 at 10:41
velikiveliki
114
add a comment |
systemctl can't possibly know the ways dynctl.sh is forking so that it could know how many child processes must be alive at a given time. That's why you have to manage the life cycle of the processes, so that when one child process is dead, the service will be restarted.
I suggest using the main process as a master for the other ones, so that by using grep or pgrep it could determine if all children processes are alive, and if not it will give the comand systemctl restart <your service>.
Cheers, hope it helps
answered Feb 19 at 10:41
velikiveliki
114
add a comment |
systemctl can't possibly know the ways dynctl.sh is forking so that it could know how many child processes must be alive at a given time. That's why you have to manage the life cycle of the processes, so that when one child process is dead, the service will be restarted.
I suggest using the main process as a master for the other ones, so that by using grep or pgrep it could determine if all children processes are alive, and if not it will give the comand systemctl restart <your service>.
Cheers, hope it helps
answered Feb 19 at 10:41
velikiveliki
114
systemctl can't possibly know the ways dynctl.sh is forking so that it could know how many child processes must be alive at a given time. That's why you have to manage the life cycle of the processes, so that when one child process is dead, the service will be restarted.
I suggest using the main process as a master for the other ones, so that by using grep or pgrep it could determine if all children processes are alive, and if not it will give the comand systemctl restart <your service>.
Cheers, hope it helps
answered Feb 19 at 10:41
velikiveliki
114
answered Feb 19 at 10:41
velikiveliki
114
answered Feb 19 at 10:41
velikiveliki
114
answered Feb 19 at 10:41
velikiveliki
114
114
add a comment |
add a comment |
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%2f1333069%2fhow-to-track-all-child-processes-spawned-by-a-systemctl-service%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
