-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WIP] Modernize start method #135
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -9,11 +9,16 @@ RefuseManualStop=true | |
RefuseManualStart=true | ||
|
||
[Service] | ||
Type=forking | ||
PIDFile=@runstatedir@/sbd.pid | ||
Type=simple | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. If we make the unit file changes a configure option defaulting to forking (for now at least), then we have backward compatibility with older pacemaker "exec" seems more useful than "simple" if we don't want to go all the way to "sd_notify" There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Well, slightly as it needs the initial fork & exec to succeed but I guess not to an extent that it is really useful for us here. |
||
# sbd-inquisitor will usually have opened a watchdog-device | ||
# thus we should give it a chance to do what | ||
# it needs to (anyway kills the subprocesses the | ||
# hard way) and close that gracefully. | ||
# If that isn't successful within time let mixed | ||
# do a cleanup although that will most likely lead to suicide. | ||
KillMode=mixed | ||
EnvironmentFile=-@CONFIGDIR@/sbd | ||
ExecStart=@sbindir@/sbd $SBD_OPTS -p @runstatedir@/sbd.pid watch | ||
ExecStop=@bindir@/kill -TERM $MAINPID | ||
ExecStart=@sbindir@/sbd $SBD_OPTS watch | ||
|
||
# Could this benefit from exit codes for restart? | ||
# Does this need to be set to msgwait * 1.2? | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If I follow correctly, with "forking", the parent doesn't exit until it gets SIG_LIVENESS. Do we need to go all the way to "sd_notify" to keep the behavior similar?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As to my knowledge I'm afraid yes.
Unless of course we totally rely on the daemons talking to each other.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The comment in inquisitor_decouple btw. is a lie - I'll remove/correct it in the course of this PR - the inquisitor decouples once cluster-servant is online - meaning it has received it's own membership.