-
Notifications
You must be signed in to change notification settings - Fork 119
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
VPN-4227: Windows daemon recovery on crash #9214
Conversation
f253ca2
to
b453ded
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.
This look reasonable, but I'm not familiar with our Windows networking code. I don't feel comfortable approving this without asking a lot of questions so I come up to speed in this area.
If @lesleyjanenorton is not comfortable approving, let me know and I'll ask questions here or set up some time to walk through it with you.
@mcleinman in light of the recent staffing changes, I think I am probably the only Windows networking expert on the team. Please feel free to ask questions. |
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.
👍
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.
Thanks to Naomi for walking through this with Lesley and I.
Description
In order to add a bit more robustness to the VPN client, we should ensure we can recovery gracefully in the event of a crash of the daemon. This adds some handling of unexpected daemon termination and takes steps to ensure that the system remains in a usable state even if a crash occurs.
Reference
Github issue #7986 (VPN-4227)
Github issue #7987 (VPN-4231)
Checklist