| 1 |
Walter Dnes wrote: |
| 2 |
> On Wed, Dec 11, 2019 at 08:37:10PM +1100, Adam Carter wrote |
| 3 |
>> chrony on the "server" to sync from the Internet and systemd-timesyncd |
| 4 |
>> on the others to sync from the server. |
| 5 |
> Sounds like something Lennart came up with. |
| 6 |
> |
| 7 |
> On Wed, Dec 11, 2019 at 11:45:57AM -0600, Dale wrote |
| 8 |
> |
| 9 |
>> I don't know how openrdate works but for chrony, set up the config file |
| 10 |
>> and then /etc/init.d/chronyd start. After a bit, you can check to see |
| 11 |
>> how close it is. If things are working well enough, don't forget to add |
| 12 |
>> it to a runlevel so that it starts when you boot up. |
| 13 |
> openrdate defaults to set correct time directly, but it does have an |
| 14 |
> optional parameter to gradually skew local time to the remote time. I |
| 15 |
> use openrdate in client mode once a month or so to sync a machine. |
| 16 |
> |
| 17 |
|
| 18 |
Well, if you use chrony as a service, you shouldn't have to do that |
| 19 |
anymore. Each time you boot it will sync up the clocks and it will keep |
| 20 |
the clock accurate from then on. I don't have a laptop but from what |
| 21 |
I've read, it even works well on those even tho they may not always be |
| 22 |
able to sync due to not always having a internet connection. Give it a |
| 23 |
little time, maybe chrony will "grow" on you. lol |
| 24 |
|
| 25 |
I updated my chrony config file to this: |
| 26 |
|
| 27 |
|
| 28 |
server 64.6.144.6 |
| 29 |
server 209.114.111.1 |
| 30 |
server 130.207.244.240 |
| 31 |
|
| 32 |
server 0.us.pool.ntp.org |
| 33 |
server 1.us.pool.ntp.org |
| 34 |
server 2.us.pool.ntp.org |
| 35 |
server 3.us.pool.ntp.org |
| 36 |
|
| 37 |
|
| 38 |
I now get this from chrony: |
| 39 |
|
| 40 |
|
| 41 |
root@fireball / # chronyc sources -v |
| 42 |
210 Number of sources = 7 |
| 43 |
|
| 44 |
.-- Source mode '^' = server, '=' = peer, '#' = local clock. |
| 45 |
/ .- Source state '*' = current synced, '+' = combined , '-' = not |
| 46 |
combined, |
| 47 |
| / '?' = unreachable, 'x' = time may be in error, '~' = time too |
| 48 |
variable. |
| 49 |
|| .- xxxx [ yyyy ] +/- zzzz |
| 50 |
|| Reachability register (octal) -. | xxxx = adjusted |
| 51 |
offset, |
| 52 |
|| Log2(Polling interval) --. | | yyyy = measured |
| 53 |
offset, |
| 54 |
|| \ | | zzzz = estimated |
| 55 |
error. |
| 56 |
|| | | \ |
| 57 |
MS Name/IP address Stratum Poll Reach LastRx Last |
| 58 |
sample |
| 59 |
=============================================================================== |
| 60 |
^- triangle.kansas.net 2 7 377 61 +3945us[+4033us] |
| 61 |
+/- 113ms |
| 62 |
^+ bindcat.fhsu.edu 2 7 377 61 -2796us[-2708us] |
| 63 |
+/- 61ms |
| 64 |
^* navobs1.gatech.edu 1 7 377 59 -3297us[-3209us] |
| 65 |
+/- 21ms |
| 66 |
^+ li924-200.members.linode> 2 7 377 60 -4993us[-4905us] |
| 67 |
+/- 28ms |
| 68 |
^- 208.67.75.242 2 7 377 128 -1448us[-1362us] |
| 69 |
+/- 83ms |
| 70 |
^+ 162.159.200.123 3 7 377 127 +13ms[ +13ms] |
| 71 |
+/- 36ms |
| 72 |
^- srcf-ntp.stanford.edu 2 7 377 128 -1876us[-1791us] |
| 73 |
+/- 58ms |
| 74 |
root@fireball / # |
| 75 |
|
| 76 |
|
| 77 |
If I average those, my clock is accurate to about 57ms. Given I'm not |
| 78 |
doing anything that requires a perfect clock, that's close enough. Can |
| 79 |
a person blink that fast??? lol I might add, either you don't mind |
| 80 |
your system being off a bit or your rig has a good built in clock. I |
| 81 |
remember my old rig having a clock that was always drifting bad. |
| 82 |
Sometimes fast, sometimes slow. I think the temps affected it. I've |
| 83 |
always had a clock tool set my clock. I don't even know how close the |
| 84 |
clock will stay on this machine. I've never tested it. |
| 85 |
|
| 86 |
Dale |
| 87 |
|
| 88 |
:-) :-) |
Archives