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