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

timesync: on network event do not establish connection when NTP servers are not changed #8611

Merged
merged 1 commit into from
Mar 29, 2018

Conversation

yuwata
Copy link
Member

@yuwata yuwata commented Mar 29, 2018

Fixes #8603.

@yuwata
Copy link
Member Author

yuwata commented Mar 29, 2018

I am not sure this is a right way to fix the issue...

@yuwata
Copy link
Member Author

yuwata commented Mar 29, 2018

This may also fix #3888.

@poettering
Copy link
Member

I like the approach.

@poettering poettering merged commit 3e85ec0 into systemd:master Mar 29, 2018
@yuwata yuwata deleted the fix-8603 branch March 29, 2018 14:22
@sitsofe
Copy link

sitsofe commented Mar 29, 2018

@yuwata @poettering You probably want to reconnect periodically (e.g. if you renew a lease and it's a day or more since you last sync'd NTP) but only doing it once per boot for a stable lease could lead to huge drifts that will never be corrected...

@yuwata
Copy link
Member Author

yuwata commented Mar 29, 2018

@sitsofe I may misunderstand your comment, but timesyncd sends a request after an interval. I do not think this makes timesyncd do 'it once per boot'.

@sitsofe
Copy link

sitsofe commented Mar 30, 2018

@yuwata No you understood perfectly and the misunderstanding was mine! You're entirely correct and your patch does indeed look fine :-).

@yuwata
Copy link
Member Author

yuwata commented Mar 30, 2018

I am happy to hear that :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

Successfully merging this pull request may close these issues.

None yet

3 participants