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