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

RFE: Add option for noselect to the timesync_ntp_servers options #191

Open
chsnell opened this issue Apr 19, 2023 · 3 comments
Open

RFE: Add option for noselect to the timesync_ntp_servers options #191

chsnell opened this issue Apr 19, 2023 · 3 comments

Comments

@chsnell
Copy link

chsnell commented Apr 19, 2023

noselect is a valid option for server & pool entries for both chronyd and ntpd. It has usefulness when you want to have a reference clock available but not utilized as a synchronization option such as in a tightly controlled network. It would be a boolean value, much the same as pool or nts.

@richm
Copy link
Collaborator

richm commented Apr 19, 2023

noselect is a valid option for server & pool entries for both chronyd and ntpd. It has usefulness when you want to have a reference clock available but not utilized as a synchronization option such as in a tightly controlled network. It would be a boolean value, much the same as pool or nts.

Would #54 allow you to set this option?

@chsnell
Copy link
Author

chsnell commented Apr 19, 2023

There is already a timesync_chrony_custom_settings which would allow it for chrony, but you would have to enter a whole line with all the settings such as:

server foo.example.com maxpoll 12 noselect

Based on the template code currently, this would add an additional entry all the way at the end of the file rather than cleanly with the rest of the server/poll lines.

I just happen to need the noselect in my configuration, but ideally I could see the code eventually being extended to support most if not all of the server/pool options to allow the role to be more fully featured.

@richm
Copy link
Collaborator

richm commented Apr 19, 2023

There is already a timesync_chrony_custom_settings which would allow it for chrony, but you would have to enter a whole line with all the settings such as:

server foo.example.com maxpoll 12 noselect

Based on the template code currently, this would add an additional entry all the way at the end of the file rather than cleanly with the rest of the server/poll lines.

I don't understand - is the order of these items significant? And if the file is being generated by the timesync role, why does the file need to be "clean"?

I just happen to need the noselect in my configuration, but ideally I could see the code eventually being extended to support most if not all of the server/pool options to allow the role to be more fully featured.

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

No branches or pull requests

2 participants