| 1 |
Am 05.03.2013 07:36, schrieb Canek Peláez Valdés: |
| 2 |
|
| 3 |
> I don't. AFAIK, systemd provides systemd-timedated(8) since systemd |
| 4 |
> 30: |
| 5 |
> |
| 6 |
> http://www.freedesktop.org/wiki/Software/systemd/timedated |
| 7 |
|
| 8 |
Yes, found that as well yesterday. |
| 9 |
|
| 10 |
> In normal desktops/laptops/servers, it just works. |
| 11 |
> |
| 12 |
>>> I *had* a hwclock.service and removed it now ... no change. |
| 13 |
>> |
| 14 |
>> Aside from being interested if to run hwclock.service: |
| 15 |
>> |
| 16 |
>> solved that by entering BIOS and correcting time (was one hour |
| 17 |
>> behind, why ever ...) |
| 18 |
> |
| 19 |
> It helps if the hardware clock is set to the correct time, yes. The |
| 20 |
> only problem is if you dual boot Windows (or so I heard). |
| 21 |
|
| 22 |
I read that it should be preferred to registry-fix the behavior in |
| 23 |
Windows. I will have a look sometimes ... I very rarely boot that win7 |
| 24 |
on my workstation. |
| 25 |
|
| 26 |
So the following service-file is unnecessary and at best redundant? |
| 27 |
|
| 28 |
# cat /etc/systemd/system/hwclock.service |
| 29 |
[Unit] |
| 30 |
Description=hwclock |
| 31 |
|
| 32 |
[Service] |
| 33 |
Type=oneshot |
| 34 |
ExecStart=/sbin/hwclock --hctosys --localtime |
| 35 |
ExecStop=/sbin/hwclock --systohc --localtime |
| 36 |
|
| 37 |
[Install] |
| 38 |
WantedBy=multi-user.target |
| 39 |
|
| 40 |
pulled that one in from arch linux or so ... |
| 41 |
|
| 42 |
Greets, Stefan |
Archives