Skip to content
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

No idle timer when not socket activated #57

Merged
merged 3 commits into from
Jun 5, 2022
Merged

No idle timer when not socket activated #57

merged 3 commits into from
Jun 5, 2022

Conversation

simo5
Copy link
Contributor

@simo5 simo5 commented Jun 5, 2022

The idle timer should definitely be disabled when socket activation is
not being used. Insure that the idle handler does not set up events
when the daemon is not in userproxy mode, and further ensure that
termination is disabled when a regular socket is initialized.

Fixes #56

@simo5
Copy link
Contributor Author

simo5 commented Jun 5, 2022

@grawity can you check if this simple patch fixes the problem for you?

simo5 added 2 commits June 4, 2022 23:04
Signed-off-by: Simo Sorce <simo@redhat.com>
Signed-off-by: Simo Sorce <simo@redhat.com>
@grawity
Copy link

grawity commented Jun 5, 2022

Thanks, it seems to be working properly.

The idle timer should definitely be disabled when socket activation is
not being used. Ensure that the idle handler does not set up events
when the daemon is not in userproxy mode, and further ensure that
termination is disabled when a regular socket is initialized.

Signed-off-by: Simo Sorce <simo@redhat.com>
@simo5 simo5 merged commit 302452e into gssapi:main Jun 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

gssproxy 0.9.0 exits when idle and crashes
2 participants