Paul, On Fri, Jun 10, 2011 at 1:05 PM, Paul Gideon Dann <pdgiddie@xxxxxxxxx> wrote: > I've found this gnawing at me since I read it. I originally started using > OpenNTPD because it was smaller, lighter, and easier to configure. However, > it's disappointing that it doesn't deal better with the hardware clock. > > Searching around for more information, I discovered that OpenNTPD is not > currently well supported for Linux, and the "portable" version that our > package is based on is lagging significantly behind the mainline. > > I've heard a few people mention Chrony as a good alternative, and I like the > sound of it. There's an AUR package, but no Wiki entry. Has anyone given > Chrony a shot, or have any strong opinions about it? I don't know about Chrony, but I was in the same situation as yourself when I found out about the status of OpenNTP. I tried installing the regular ntpd, and it was actully very simple to set up, and not particularly huge, so I'm using that. PS A solution for OpenNTP is to call "hwclock --systohc" when it stops. -t
