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