-
Notifications
You must be signed in to change notification settings - Fork 245
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
MONITOR: fix socket_activated
flag initialization
#6575
MONITOR: fix socket_activated
flag initialization
#6575
Conversation
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.
Two minor changes in your commit message:
s/for a first/for the first
s/patch moves moves/patch moves
a898e85
to
0994901
Compare
@spoore1, could you please help - what is better in this context? |
I believe 'for the first time' is correct in this context. |
When socket activated service connects for the first time, it is added to `mt_ctx->svc_list` by `socket_activated_service_not_found()` with a proper `socket_activated = true`. But when it reconnects again, `get_service_in_the_list()` finds it in `mt_ctx->svc_list` and overwrites `socket_activated = false` unconditionally. This patch moves `socket_activated = false` to `start_service()`. Resolves: SSSD#6324
0994901
to
e0f2079
Compare
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.
LGTM. Thanks for the patch!
When socket activated service connects for a first time, it is added to
mt_ctx->svc_list
bysocket_activated_service_not_found()
with a propersocket_activated = true
.But when it reconnects again,
get_service_in_the_list()
finds it inmt_ctx->svc_list
and overwritessocket_activated = false
unconditionally. This patch moves movessocket_activated = false
tostart_service()
.Resolves: #6324