[systemd-bugs] [Bug 86292] New: systemd-timesyncd: Do not save clock to disk on every NTP fix

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=86292

            Bug ID: 86292
           Summary: systemd-timesyncd: Do not save clock to disk on every
                    NTP fix
           Product: systemd
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: trivial
          Priority: medium
         Component: general
          Assignee: systemd-bugs at lists.freedesktop.org
          Reporter: philipp.reinkemeier at offis.de
        QA Contact: systemd-bugs at lists.freedesktop.org

Hi.
I have a system running with systemd-networkd and systemd-resolved. Main HDD is
an external USB drive. Of course to have a long lifetime of that drive i want
it to spin up as few times as possible. Recently i discovered systemd-timesyncd
and wanted to use that instead of the standard ntp client server
implementation.
However i discovered that systemd-timesyncd saves the current clock value to
disk ("/var/lib/systemd/clock") every time it gets a new NTP fix. It seems this
behavior is introduced by the following commit
http://cgit.freedesktop.org/systemd/systemd/commit/?id=ece6e766cf89c8ec82ad135969dedf16cd7c1ee8.
While i see the usefulness of saving the clock to disk and restore it on the
next start of the daemon, i do not understand why this has to happen on every
NTP fix. Isn't it sufficient to save the clock value to disk when the daemon
terminates? This has also been introduced by the commit above. Doing it that
way would prevent unnecessary disk accesses during runtime of the daemon.

To sum up: This is a request to remove the call to "save_clock()" from within
the "manager_adjust_clock(...)" function.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20141114/d8417288/attachment.html>