This is the
talk page for discussing improvements to the
Network Time Protocol article. This is not a forum for general discussion of the article's subject. |
Article policies
|
Find sources: Google ( books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL |
Archives: 1Auto-archiving period: 365 days |
This article is rated B-class on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||||||||||||||||||||||
|
Note: This text above was added by an IP address user coming in from 92.208.243.129 at 10:44, 26 March 2021
As I write this, the article has the sentence "It is also designed for virtual machines, a more unstable environment." under the chrony section. The main chrony article in the Wikipedia does not contain "virtual" or "VM" so it doesn't support this claim. The reference attached to that sentence (Both, David. "Manage NTP with Chrony". Opensource.com. Archived from the original on 29 June 2019. Retrieved 29 June 2019 https://web.archive.org/web/20190629174030/https://opensource.com/article/18/12/manage-ntp-chrony) does not make any such claim.
I suggest that the sentence (and reference) be removed. MabryTyson ( talk) 21:14, 19 June 2023 (UTC)
That's a common, but incomplete and sometimes confusing description. For example, later on we see: "[W32time] The version in Windows 2000 and Windows XP only implements SNTP".
But SNTP is the same networking protocol as NTP, and Win32time on XP and 2000 "has the ability to synchronize the computer clock to an NTP server"
The problems of course are that (1) the XP time server lacks "NTP's data analysis and clock disciplining algorithms", which is time server clock synchronization protocol, and (2) the word "synchronization" has been used in two different senses: NTP disciplined synchronization, and SNTP occasional synchronization. 121.200.27.15 ( talk) 04:52, 3 May 2024 (UTC)
This is the
talk page for discussing improvements to the
Network Time Protocol article. This is not a forum for general discussion of the article's subject. |
Article policies
|
Find sources: Google ( books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL |
Archives: 1Auto-archiving period: 365 days |
This article is rated B-class on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||||||||||||||||||||||
|
Note: This text above was added by an IP address user coming in from 92.208.243.129 at 10:44, 26 March 2021
As I write this, the article has the sentence "It is also designed for virtual machines, a more unstable environment." under the chrony section. The main chrony article in the Wikipedia does not contain "virtual" or "VM" so it doesn't support this claim. The reference attached to that sentence (Both, David. "Manage NTP with Chrony". Opensource.com. Archived from the original on 29 June 2019. Retrieved 29 June 2019 https://web.archive.org/web/20190629174030/https://opensource.com/article/18/12/manage-ntp-chrony) does not make any such claim.
I suggest that the sentence (and reference) be removed. MabryTyson ( talk) 21:14, 19 June 2023 (UTC)
That's a common, but incomplete and sometimes confusing description. For example, later on we see: "[W32time] The version in Windows 2000 and Windows XP only implements SNTP".
But SNTP is the same networking protocol as NTP, and Win32time on XP and 2000 "has the ability to synchronize the computer clock to an NTP server"
The problems of course are that (1) the XP time server lacks "NTP's data analysis and clock disciplining algorithms", which is time server clock synchronization protocol, and (2) the word "synchronization" has been used in two different senses: NTP disciplined synchronization, and SNTP occasional synchronization. 121.200.27.15 ( talk) 04:52, 3 May 2024 (UTC)