<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED NOTABUG - RFE: systemd-timesyncd: Do not save clock to disk on every NTP fix"
href="https://bugs.freedesktop.org/show_bug.cgi?id=86292#c7">Comment # 7</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED NOTABUG - RFE: systemd-timesyncd: Do not save clock to disk on every NTP fix"
href="https://bugs.freedesktop.org/show_bug.cgi?id=86292">bug 86292</a>
from <span class="vcard"><a class="email" href="mailto:lotus@blossomhillranch.com" title="lotus@blossomhillranch.com">lotus@blossomhillranch.com</a>
</span></b>
<pre>I'm running arch on a Raspberry Pi. I'd greatly prefer that the time not be set
instead of being set wrong.
I tried the /dev/null trick above and it doesn't work 100%. During boot I get
this:
Dec 31 16:00:10.739020 captureserver systemd-timesyncd[129]: System clock time
unset or jumped backwards, restoring from recorded timestamp: Mon 2015-02-16
12:55:07 PST
I'd like the option to leave the clock alone until it contacts a NTP server. A
setting in timesyncd.conf would be great.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>