Description of problem: With new ntpd and chronyd versions that are planned to be included in Fedora 22, the default configuration files will likely be changed to use the pool directive instead of server. This is used to specify a group of NTP servers where unreachable servers are replaced automatically. Instead of the four individial servers specified in the config server 0.fedora.pool.ntp.org iburst server 1.fedora.pool.ntp.org iburst server 2.fedora.pool.ntp.org iburst server 3.fedora.pool.ntp.org iburst there will be just one pool directive pool fedora.pool.ntp.org iburst It would be nice if system-config-date supported this. I'm not sure what would be the best way to present this to the user, maybe a checkbox for each entry that would switch between pool and server? Or resolve the name and see if the name resolves to multiple IPv4/IPv6 addresses to select it automatically?
Created attachment 987113 [details] Add support for pool directive to system-config-date Display four servers with the same name for each pool directive. When writing config, count servers with the same name and select pool or server directive as appropriate.
The pool directive is now used in the default chrony.conf (chrony-2.0-0.2.pre1). The name used is 2.fedora.pool.ntp.org, because it's currently the only one returning IPv6 addresses. ntp will follow after update to 4.2.8.
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
*** Bug 1226568 has been marked as a duplicate of this bug. ***
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.