If true, the host will use NTP to sync its clock with time values retrieved from other servers.
In addition to being an NTP client, this host will act as an NTP server. This configuration allows local network devices to use the host as a source of NTP data. Local network devices will also be able to query this host for additional NTP runtime information.
In addition to being an NTP client, this host will act as an NTP server. This configuration allows local network devices to use the host as a source of NTP data. Unlike "Server", local network devices will be unable to query this host for additional NTP runtime information.
This host will act as an NTP client only. The NTP data retrieved by this host from configured servers will not be available to local network devices.
If true, the host will start the Network Time Protocol daemon. This boolean does not directly say that NTP will be used as a time source on this platform, rather, it enables that option.
Additional properties below will inform the NTP daemon how time information now available will be used.
Default is false. If true, when the JACE boots, before the stations starts or the ntpd starts, it executes the ntpdate command. This updates the system local time.
If true, should the specified NTP server(s) become unavailable at the time of a poll, the time used is provided by the system clock. This prevents the timing of the polling algorithm in the ntpd (which is executed at specified/changing intervals) from being reset.
A true value does not result in any change to the NTP daemon’s polling interval (frequency). In fact, by using the local system clock the NTP-calculated polling time would remain the same, and thus not result in more polling.
If true, the NtpPlatformService reports whatever information it can about its operation. To access these statistics with the
station opened in