-
Notifications
You must be signed in to change notification settings - Fork 220
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
fix: Watch sysctl changes to ensure expected values #426
Conversation
A typical process is systemd-sysctl. |
5c4aa21
to
78690e9
Compare
Almost ready to merge. Thanks for your great work! |
78690e9
to
3df979c
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.
🧪 Since the PR has been fully tested, please consider merging it.
4019fb4
89585b1
to
4019fb4
Compare
I have dae v0.5.1 installed, got: |
@douglarek Did you see connectivity issues? If so, did you see warn or error log? |
This info log is printed only when starting the daemon (dae), with no other related warning or error logs. |
@douglarek What kind of connectivity issue did you have? |
Not yet. |
@douglarek It's an info log, no worries, unless connectivity is broken. |
Background
We noticed some process other than dae will change dae0's sysctl and break the connectivity from dae netns.
This PR fixes the issue by inotify watching the sysctl files and ensure expected values are set.
Checklist
Full Changelogs
Issue Reference
This PR proposes some optimization against #414
Test Result