| 1 |
On 07/26/2014 11:25 PM, Dale wrote: |
| 2 |
> Alexander Kapshuk wrote: |
| 3 |
>> On 07/26/2014 03:31 PM, Holger Hoffstätte wrote: |
| 4 |
>>> On Sat, 26 Jul 2014 15:05:23 +0300, Alexander Kapshuk wrote: |
| 5 |
>>> |
| 6 |
>>>> Which NTPd package would the list recommend using, ntp, openntpd, or |
| 7 |
>>>> some other package? |
| 8 |
>>> chrony - no competition, even for servers. ntpd is way overrated, |
| 9 |
>>> unnecessarily hard to setup correctly, fragile and contrary to |
| 10 |
>>> popular belief not even that accurate, unless you use external |
| 11 |
>>> HW clocks. Chrony is maintained by Red Hat in cooperation with the |
| 12 |
>>> timekeeping code in the kernel. |
| 13 |
>>> |
| 14 |
>>>> openntpd seems to be easier to set up according to wiki.gentoo.org. |
| 15 |
>>> Many many years ago I helped port openntpd to Linux. It was OK-ish at |
| 16 |
>>> the time and easier/less hassle than ntpd, but the portable version for |
| 17 |
>>> Linux stopped working reliably many years ago due to kernel changes. |
| 18 |
>>> IMHO it really should no longer be in the tree since it gives a false |
| 19 |
>>> sense of accuracy. |
| 20 |
>>> |
| 21 |
>>> just my 0.01€.. |
| 22 |
>>> |
| 23 |
>>> -h |
| 24 |
>>> |
| 25 |
>>> |
| 26 |
>> Is this gentoo wiki article still relevant when it comes to configuring |
| 27 |
>> chrony on gentoo? |
| 28 |
>> http://www.gentoo-wiki.info/Chrony |
| 29 |
>> |
| 30 |
>> Or should I stick to the instructions given here: |
| 31 |
>> /usr/share/doc/chrony-1.29.1/chrony.txt.bz2 |
| 32 |
>> |
| 33 |
>> Thanks. |
| 34 |
>> |
| 35 |
>> |
| 36 |
>> |
| 37 |
> |
| 38 |
> This is my chrony.conf without all the commented out parts. |
| 39 |
> |
| 40 |
> server 64.6.144.6 |
| 41 |
> server 67.159.5.90 |
| 42 |
> server 67.59.168.233 |
| 43 |
> server 204.62.14.98 |
| 44 |
> |
| 45 |
> server 69.50.219.51 |
| 46 |
> server 209.114.111.1 |
| 47 |
> |
| 48 |
> driftfile /etc/chrony.drift |
| 49 |
> |
| 50 |
> keyfile /etc/chrony/chrony.keys |
| 51 |
> |
| 52 |
> commandkey 1 |
| 53 |
> |
| 54 |
> logdir /var/log/chrony |
| 55 |
> log measurements statistics tracking rtc |
| 56 |
> |
| 57 |
> |
| 58 |
> The last two lines are optional. Use those if you like to be nosy and |
| 59 |
> watch it do its thing. I still have ntpdate installed and use it to |
| 60 |
> check and see how close it is on occasion. This is what I get from the |
| 61 |
> test: |
| 62 |
> |
| 63 |
> root@fireball / # ntpdate -b -u -q pool.ntp.org |
| 64 |
> server 198.144.194.12, stratum 2, offset -0.003320, delay 0.10658 |
| 65 |
> server 173.44.32.10, stratum 2, offset -0.003313, delay 0.07515 |
| 66 |
> server 70.60.65.40, stratum 2, offset -0.003059, delay 0.09262 |
| 67 |
> server 38.229.71.1, stratum 2, offset -0.001002, delay 0.09563 |
| 68 |
> 26 Jul 15:16:00 ntpdate[10232]: step time server 173.44.32.10 offset |
| 69 |
> -0.003313 sec |
| 70 |
> root@fireball / # |
| 71 |
> |
| 72 |
> I did a fair sized upgrade the other day and went to the boot runlevel |
| 73 |
> afterwards to restart the services that were updated. I'm pretty sure |
| 74 |
> it has been doing its thing since then without me doing anything to it. |
| 75 |
> I think you can use mirrorselect to find the best mirrors for your |
| 76 |
> area. I can't recall the command but I bet a search of the Gentoo |
| 77 |
> forums would find it fairly quick. |
| 78 |
> |
| 79 |
> Looking at the howto, the only thing I do different is put it in the |
| 80 |
> default runlevel. Unless I am in the default runlevel, there is no |
| 81 |
> internet access available anyway. No internet access, no way to set the |
| 82 |
> clock anyway. ;-) |
| 83 |
> |
| 84 |
> Hope that helps. |
| 85 |
> |
| 86 |
> Dale |
| 87 |
> |
| 88 |
> :-) :-) |
| 89 |
> |
| 90 |
Terrific. Thanks. |
Archives