Paul,
On Fri, Jun 10, 2011 at 1:05 PM, Paul Gideon Dann 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.
>
>
On Saturday 04 June 2011 08:44:34 Jan de Groot wrote:
> On Sat, 2011-06-04 at 03:06 -0400, Yclept Nemo wrote:
> > Perhaps openntpd does not set the hwclock. Therefore, should openntpd
> > be used in conjuction with the hwclock daemon?
>
> That's true, and that's also the reason why Openntpd doesn'
Jan de Groot :
> On Sat, 2011-06-04 at 03:06 -0400, Yclept Nemo wrote:
> > Perhaps openntpd does not set the hwclock. Therefore, should
> > openntpd be used in conjuction with the hwclock daemon?
>
> That's true, and that's also the reason why Openntpd doesn't play
> well with Xen where all gues
On Sat, 2011-06-04 at 03:06 -0400, Yclept Nemo wrote:
> Perhaps openntpd does not set the hwclock. Therefore, should openntpd
> be used in conjuction with the hwclock daemon?
That's true, and that's also the reason why Openntpd doesn't play well
with Xen where all guest VMs will take over the clo
A recent announcement said:
* The adjustment of the hwclock for drift is moved into a daemon that should
not be used in most scenarios as it can lead to subtle bugs (especially if using
dual-boot or ntp). If you know what you are doing and want to adjust the
hardware clock for drift, add `"hwcloc
5 matches
Mail list logo
