mlichvar

7 ms·

31.
by mlichvar 7y ago
Yes, but NTP as a time service (client/server mode) is safe. A request has a single response and their lengths are symmetric (that's actually a requirement for accurate synchronization). The problem with amplification is in the op
32.
by mlichvar 7y ago
PTP over Internet doesn't make much sense. PTP requires hardware support in all network devices on the path between the (grand)master and slave. Without this support it will generally perform worse than NTP. Of course, it depends also
33.
by mlichvar 8y ago
Another possibility to improve reliability with SD cards is to use a distro that is designed to not make any writes to the storage in normal operation. I have some NTP servers running on OpenWRT and they work great.
34.
by mlichvar 8y ago
Good support for PTP in network switches is rare. If the users don't want to spend a lot of money on new switches with PTP support, they can synchronize clocks in the network with a protocol which doesn't require special support i
35.
by mlichvar 8y ago
I maintain an NTP implementation. That comparison doesn't seem fair to me. It looks like they are comparing the old reference NTP implementation and not really the protocol itself. An NTP implementation can certainly synchronize clocks
36.
by mlichvar 9y ago
> Just saying "Yes" here is highly misleading. FWIW, the page also compares the number of reference clock drivers. chrony does not have any HW-specific drivers, but there is an interface which other programs can use to provide
37.
by mlichvar 10y ago
xterm is showing all data. That's why it's slower. For a fair comparison, you should set the fastScroll X resource, which will allow xterm to suppress screen refresh.
38.
by mlichvar 11y ago
The problem with this solution is that it's very expensive. Imagine couple hundreds of millions of computers making a TLS connection every few minutes. For NTP there is Autokey (RFC 5906), which allows authentication of the servers wit
39.
by mlichvar 11y ago
Writing new implementations of the systemd interfaces for systems which don't use systemd seems reasonable, but I think it's interesting there was a need to reimplement the timedated interface on a system that does use systemd and
40.
by mlichvar 11y ago
chrony maintainer here. If the initial sync is slow, it probably means the initial offset of the clock is large and chronyd is correcting it by slewing, which may take a long time. You can use the initstepslew or makestep directive to step