Age | Commit message (Collapse) | Author |
|
This fix changes the way that the /etc/ntp.conf file is generated. Now
it is generated at boot time using a fixed section that contains
only parameters that users don't change, plus a section that is generated
from any "system ntp-servers" parameters that are configured. The fixed
section does not contain any "server" definitions, so all server definitions
come from the Vyatta config.
The Vyatta configuration template for this parameter and code
at other places in the system will now start the NTP server ONLY if
there is at least one NTP server configured. So the user can "turn off"
the NTP server by just deleting all NTP servers from the configuration.
The default "config.boot" file does contiain one built-in "system ntp-servers"
parameter, so a newly installed system will start the NTP server.
|
|
Only put comments in about features that are used.
|
|
|
|
So when CLI updates ntp.conf, the file stays same format
|
|
There are options (like restrict) that should be ntp.conf
This would reduce security exposure of the router (see recent CVE).
Also, this avoid restarting ntp server on boot when using the default
vyatta ntp server.
|