On Tue, Oct 16, 2012 at 11:10:21AM +0200, Thomas Bächler wrote: > Am 16.10.2012 03:56, schrieb Martín Cigorraga: > > On Mon, Oct 15, 2012 at 10:50 PM, Gaetan Bisson <bisson@xxxxxxxxxxxxx>wrote: > > > >> [2012-10-15 22:25:58 -0300] Martín Cigorraga: > >>> Basically I need to know how to handle these daemons: > >>> hwclock > >> > >> Ditch it. Use NTP instead: > > I think systemd does hwclock handling in some way. However, you should > always run NTP, on every machine, real or virtual. > systemd reimplements the bare minimum of hwclock(8) to "seal" the kernel timezone, as the first call to settimeofday(2) on bootup is special. The userspace timezone used will warp the kernel's clock by a given number of minutes -- this means 0 for UTC, and some non-zero value for localtime (UTC offset in hours * 60). This is an ugly hack, and part of why it's never recommended to run with the BIOS clock in localtime. Any regular adjustment of the hwclock should be handled by an NTP daemon, which can read from an authoritative source. d
