Hi,

systemd has incorparted fake-hwclock -like functionality since v213 &
I haven't used fake-hwclock since,
I guess this silly .gif is not up-to-date:

https://lh3.googleusercontent.com/-bZId5j2jREQ/U-vlysklvCI/AAAAAAAACrA/B4JggkVJi38/w426-h284/bd0fb252416206158627fb0b1bff9b4779dca13f.gif

Anyway, here is an exercpt from the last version of this service file
I found in /etc; the only things I tweaked further
are the "Before=systemd-journald.service" because I didn't liked
seeing 1970-01-01 in the journal
and "Conflicts=shutdown.target", this line may actually helps you
solve your problem.

/lib/systemd/system/systemd-timesyncd.service also includes the same
"Conflicts=".

---

[Unit]
Description=Restore / save the current clock
Documentation=man:fake-hwclock(8)
DefaultDependencies=no
Before=systemd-journald.service
Conflicts=shutdown.target

Alexandre Detiste


----

http://lists.freedesktop.org/archives/systemd-devel/2014-May/019537.html

          The daemon saves the
          current clock to disk every time a new NTP sync has been
          acquired, and uses this to possibly correct the system clock
          early at bootup, in order to accommodate for systems that
          lack an RTC such as the Raspberry Pi and embedded devices,
          and make sure that time monotonically progresses on these
          systems, even if it is not always correct.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to