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.

Sign up for GitHub

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

Jump to bottom

Support chrony for time syncing #117

Open
zmarano opened this issue Jul 2, 2021 · 2 comments
Open

Support chrony for time syncing #117

zmarano opened this issue Jul 2, 2021 · 2 comments
Assignees
@hopkiw

Comments

@zmarano
Copy link
Contributor

zmarano commented Jul 2, 2021

We currently only try to call ntpdate when syncing the clock after a migration event. However, most newer distros use chrony (or something else). Re-evaluate this code and maybe look at the default ntp client.
@zmarano
Copy link
Contributor Author

zmarano commented Jul 2, 2021

/assign @hopkiw

@hopkiw
Copy link
Contributor

hopkiw commented Jul 2, 2021

hm, ntpdate is not ntpd, the ntpd->chrony change doesn't impact ntpdate. but i see ntpdate isnt widely installed anyway and is deprecated in favor of sntp.

patelne pushed a commit to patelne/guest-agent that referenced this issue Feb 17, 2022
@zmarano
Fix gcs url vars. (GoogleCloudPlatform#117)
1adc7e5
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@hopkiw hopkiw

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@zmarano @hopkiw