doc: update links to chrony website
This commit is contained in:
parent
f74e4cf1fe
commit
25cc84d5e2
5 changed files with 6 additions and 6 deletions
2
README
2
README
|
@ -47,7 +47,7 @@ Frequently Asked Questions (FAQ).
|
||||||
The documentation is also available on the chrony web pages, accessible
|
The documentation is also available on the chrony web pages, accessible
|
||||||
through the URL
|
through the URL
|
||||||
|
|
||||||
https://chrony.tuxfamily.org/
|
https://chrony-project.org/
|
||||||
|
|
||||||
License
|
License
|
||||||
=======
|
=======
|
||||||
|
|
|
@ -3137,7 +3137,7 @@ dumpdir @CHRONYRUNDIR@
|
||||||
== BUGS
|
== BUGS
|
||||||
|
|
||||||
For instructions on how to report bugs, please visit
|
For instructions on how to report bugs, please visit
|
||||||
https://chrony.tuxfamily.org/.
|
https://chrony-project.org/.
|
||||||
|
|
||||||
== AUTHORS
|
== AUTHORS
|
||||||
|
|
||||||
|
|
|
@ -1548,7 +1548,7 @@ The *help* command displays a summary of the commands and their arguments.
|
||||||
== BUGS
|
== BUGS
|
||||||
|
|
||||||
For instructions on how to report bugs, please visit
|
For instructions on how to report bugs, please visit
|
||||||
https://chrony.tuxfamily.org/.
|
https://chrony-project.org/.
|
||||||
|
|
||||||
== AUTHORS
|
== AUTHORS
|
||||||
|
|
||||||
|
|
|
@ -217,7 +217,7 @@ _@SYSCONFDIR@/chrony.conf_
|
||||||
== BUGS
|
== BUGS
|
||||||
|
|
||||||
For instructions on how to report bugs, please visit
|
For instructions on how to report bugs, please visit
|
||||||
https://chrony.tuxfamily.org/.
|
https://chrony-project.org/.
|
||||||
|
|
||||||
== AUTHORS
|
== AUTHORS
|
||||||
|
|
||||||
|
|
|
@ -40,7 +40,7 @@ on an isolated network with no hardware reference clocks in sight, `chrony`
|
||||||
will probably work better for you.
|
will probably work better for you.
|
||||||
|
|
||||||
For a more detailed comparison of features and performance, see the
|
For a more detailed comparison of features and performance, see the
|
||||||
https://chrony.tuxfamily.org/comparison.html[comparison page] on the `chrony`
|
https://chrony-project.org/comparison.html[comparison page] on the `chrony`
|
||||||
website.
|
website.
|
||||||
|
|
||||||
=== Should I prefer `chrony` over `timesyncd` if I do not need to run a server?
|
=== Should I prefer `chrony` over `timesyncd` if I do not need to run a server?
|
||||||
|
@ -50,7 +50,7 @@ Generally, yes.
|
||||||
`systemd-timesyncd` is a very simple NTP client included in the `systemd`
|
`systemd-timesyncd` is a very simple NTP client included in the `systemd`
|
||||||
suite. It lacks almost all features of `chrony` and other advanced client
|
suite. It lacks almost all features of `chrony` and other advanced client
|
||||||
implementations listed on the
|
implementations listed on the
|
||||||
https://chrony.tuxfamily.org/comparison.html[comparison page]. One of its main
|
https://chrony-project.org/comparison.html[comparison page]. One of its main
|
||||||
limitations is that it cannot poll multiple servers at the same time and detect
|
limitations is that it cannot poll multiple servers at the same time and detect
|
||||||
servers having incorrect time (falsetickers in the NTP terminology). It should
|
servers having incorrect time (falsetickers in the NTP terminology). It should
|
||||||
be used only with trusted reliable servers, ideally in local network.
|
be used only with trusted reliable servers, ideally in local network.
|
||||||
|
|
Loading…
Reference in a new issue