On Tue, Mar 5, 2013 at 12:36 AM, Canek Peláez Valdés <can...@gmail.com> wrote: > On Mon, Mar 4, 2013 at 2:07 PM, Stefan G. Weichinger <li...@xunil.at> wrote: >> Am 04.03.2013 20:42, schrieb Stefan G. Weichinger: >>> Next systemd-issue (yes, I know ... openrc is there as well ...): >>> >>> I get warnings like "superblock date is in the future --- REPAIRED" for >>> filesystems at boot-time. >>> >>> Canek, (how) do you handle time and hwclock with systemd? > > I don't. AFAIK, systemd provides systemd-timedated(8) since systemd 30: > > http://www.freedesktop.org/wiki/Software/systemd/timedated > > In normal desktops/laptops/servers, it just works. > >>> I *had* a hwclock.service and removed it now ... no change. >> >> Aside from being interested if to run hwclock.service: >> >> solved that by entering BIOS and correcting time (was one hour behind, >> why ever ...) > > It helps if the hardware clock is set to the correct time, yes. The > only problem is if you dual boot Windows (or so I heard).
Sorry, long trip, just got home. I messed up NTP with hwclock. Anyway, I don't handle hwclock either: it's basically included in systemd: http://cgit.freedesktop.org/systemd/systemd/tree/src/shared/hwclock.c Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
