| 1 |
Walter Dnes wrote: |
| 2 |
> On Tue, Dec 10, 2019 at 03:19:16AM -0600, Dale wrote |
| 3 |
> |
| 4 |
>> I think I used ntpdate years ago. Can't recall why I switched but |
| 5 |
>> something wasn't working right. People here recommended chrony and once |
| 6 |
>> set up, its worked ever since. OP, if you haven't tried it yet, may be |
| 7 |
>> worth giving it a test run. |
| 8 |
> Now what? I'm willing to RTFM, but I can't FTFM (Find the F****** |
| 9 |
> Manual). |
| 10 |
> |
| 11 |
> ======================================================================= |
| 12 |
> |
| 13 |
> strip: x86_64-pc-linux-gnu-strip --strip-unneeded -N __gentoo_check_ldflags__ -R .comment -R .GCC.command.line -R .note.gnu.gold-version |
| 14 |
> /usr/bin/chronyc |
| 15 |
> /usr/sbin/chronyd |
| 16 |
> |
| 17 |
|
| 18 |
I have no idea what this part is doing. |
| 19 |
|
| 20 |
>>>> Installing (1 of 1) net-misc/chrony-3.5-r2::gentoo |
| 21 |
>>>> Recording net-misc/chrony in "world" favorites file... |
| 22 |
>>>> Auto-cleaning packages... |
| 23 |
>>>> No outdated packages were found on your system. |
| 24 |
> * GNU info directory index is up-to-date. |
| 25 |
> [i660][root][~] man chrony |
| 26 |
> No manual entry for chrony |
| 27 |
> [i660][root][~] info chrony |
| 28 |
> info: No menu item 'chrony' in node '(dir)Top' |
| 29 |
> [i660][root][~] emerge --unmerge chrony |
| 30 |
> |
| 31 |
> ======================================================================= |
| 32 |
> |
| 33 |
> Has RFC868 been deprecated everywhere, or is it just ca.pool.ntp.org |
| 34 |
> that won't listen to it? |
| 35 |
> |
| 36 |
|
| 37 |
|
| 38 |
When I set up chrony, I just set up the config file and then started the |
| 39 |
service. After that, it just runs and does its work. If it helps, this |
| 40 |
is my chrony.conf file. |
| 41 |
|
| 42 |
|
| 43 |
|
| 44 |
root@fireball / # cat /etc/chrony/chrony.conf |
| 45 |
# Use public NTP servers from the pool.ntp.org project. |
| 46 |
#pool pool.ntp.org iburst |
| 47 |
|
| 48 |
### SPECIFY YOUR NTP SERVERS |
| 49 |
# Most computers using chrony will send measurement requests to one or |
| 50 |
# more 'NTP servers'. You will probably find that your Internet Service |
| 51 |
# Provider or company have one or more NTP servers that you can specify. |
| 52 |
# Failing that, there are a lot of public NTP servers. There is a list |
| 53 |
# you can access at http://support.ntp.org/bin/view/Servers/WebHome or |
| 54 |
# you can use servers from the pool.ntp.org project. |
| 55 |
|
| 56 |
server 64.6.144.6 |
| 57 |
server 67.159.5.90 |
| 58 |
server 67.59.168.233 |
| 59 |
server 204.62.14.98 |
| 60 |
|
| 61 |
server 69.50.219.51 |
| 62 |
server 209.114.111.1 |
| 63 |
|
| 64 |
|
| 65 |
|
| 66 |
# Record the rate at which the system clock gains/losses time. |
| 67 |
driftfile /var/lib/chrony/drift |
| 68 |
|
| 69 |
# Allow the system clock to be stepped in the first three updates |
| 70 |
# if its offset is larger than 1 second. |
| 71 |
makestep 1.0 3 |
| 72 |
|
| 73 |
# Enable kernel synchronization of the real-time clock (RTC). |
| 74 |
rtcsync |
| 75 |
root@fireball / # |
| 76 |
|
| 77 |
|
| 78 |
After that, just do a /etc/init.d/chronyd start and it will get the |
| 79 |
clock synced and keep it that way. |
| 80 |
|
| 81 |
I found the manual here. It was the first hit on google for me. |
| 82 |
|
| 83 |
https://chrony.tuxfamily.org/documentation.html |
| 84 |
|
| 85 |
I'm no chrony expert by any measure. For me, the hardest part was |
| 86 |
finding the fastest servers. I think I use that mirrorselect tool, I |
| 87 |
think. Its been a while. |
| 88 |
|
| 89 |
Hope that helps. |
| 90 |
|
| 91 |
Dale |
| 92 |
|
| 93 |
:-) :-) |
Archives