On Tue, Dec 10, 2019 at 11:14:48PM -0600, Dale wrote > Walter Dnes wrote: > > > ======================================================================= > > > > strip: x86_64-pc-linux-gnu-strip --strip-unneeded -N > > __gentoo_check_ldflags__ -R .comment -R .GCC.command.line -R > > .note.gnu.gold-version > > /usr/bin/chronyc > > /usr/sbin/chronyd > > > > I have no idea what this part is doing.
That is approaching the end of the "emerge chrony" process. I wanted to show that I've installed chrony. > > >>>> Installing (1 of 1) net-misc/chrony-3.5-r2::gentoo > >>>> Recording net-misc/chrony in "world" favorites file... > >>>> Auto-cleaning packages... > >>>> No outdated packages were found on your system. > > * GNU info directory index is up-to-date. > > [i660][root][~] man chrony > > No manual entry for chrony > > [i660][root][~] info chrony > > info: No menu item 'chrony' in node '(dir)Top' > > [i660][root][~] emerge --unmerge chrony > > > > ======================================================================= > I found the manual here. It was the first hit on google for me. > > https://chrony.tuxfamily.org/documentation.html > Hope that helps. Thanks. From that webpage... > 2.7. Does chronyd have an ntpdate mode? > > Yes. With the -q option chronyd will set the system clock once and > exit. With the -Q option it will print the measured offset without > setting the clock. If you don't want to use a configuration file, > NTP servers can be specified on the command line. For example: > > # chronyd -q 'pool pool.ntp.org iburst' So I ran a script 3 times... #!/bin/bash date chronyd -q 'pool ca.pool.ntp.org iburst' date ...and I got... [i660][root][~] ./settime Wed 11 Dec 2019 12:18:45 PM EST 2019-12-11T17:18:45Z chronyd version 3.5 starting (+CMDMON +NTP +REFCLOCK +RTC -PRIVDROP +SCFILTER -SIGND +ASYNCDNS -SECHASH -IPV6 -DEBUG) 2019-12-11T17:18:50Z System clock wrong by 0.574369 seconds (step) 2019-12-11T17:18:51Z chronyd exiting Wed 11 Dec 2019 12:18:51 PM EST [i660][root][~] ./settime Wed 11 Dec 2019 12:19:06 PM EST 2019-12-11T17:19:06Z chronyd version 3.5 starting (+CMDMON +NTP +REFCLOCK +RTC -PRIVDROP +SCFILTER -SIGND +ASYNCDNS -SECHASH -IPV6 -DEBUG) 2019-12-11T17:19:12Z System clock wrong by -0.000421 seconds (step) 2019-12-11T17:19:12Z chronyd exiting Wed 11 Dec 2019 12:19:12 PM EST [i660][root][~] ./settime Wed 11 Dec 2019 12:19:18 PM EST 2019-12-11T17:19:18Z chronyd version 3.5 starting (+CMDMON +NTP +REFCLOCK +RTC -PRIVDROP +SCFILTER -SIGND +ASYNCDNS -SECHASH -IPV6 -DEBUG) 2019-12-11T17:19:23Z System clock wrong by -0.000084 seconds (step) 2019-12-11T17:19:23Z chronyd exiting Wed 11 Dec 2019 12:19:23 PM EST I'm not totally happy that I have to run it 3 times, but I can do that in the script. I prefer openrdate's approach where it gets the exact time once. What's with this "step" fetish? -- Walter Dnes <waltd...@waltdnes.org> I don't run "desktop environments"; I run useful applications
