From mboxrd@z Thu Jan  1 00:00:00 1970
User-Agent: Cyrus-JMAP/3.1.7-238-g170a812-fmstable-20190913v1
Mime-Version: 1.0
Message-Id: <a8a72f9f-fede-417c-8d9a-49ae3d365e38@www.fastmail.com>
In-Reply-To: <CALp9=o+xMY-LWpL98BB4vmQpCO1sjMcDtqzAtpb+vK3xFm+58g@mail.gmail.com>
References: <CALp9=o+xMY-LWpL98BB4vmQpCO1sjMcDtqzAtpb+vK3xFm+58g@mail.gmail.com>
Date: Wed, 18 Sep 2019 19:14:29 +0100
From: "Ethan Gardener" <eekee57@fastmail.fm>
To: 9fans@9fans.net
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [9fans] aux/timesync -n doesn't work
Topicbox-Message-UUID: 088d1cfc-eada-11e9-9d60-3106f5b1d025

On Tue, Sep 10, 2019, at 3:20 PM, =D0=9E=D0=BB=D0=B5=D0=B3 =D0=91=D0=B0=D1=
=85=D0=B0=D1=80=D0=B5=D0=B2 wrote:
> aux/timesync doesnt work in raspberry pi 2. How to fix this problem ?

I could never get it working until I did this:

term% cat /rc/bin/termrc.local
# timesync
# when timesync(8) says "$ntp", it's lying.
rm -f /sys/log/timesync
TIMESYNCARGS=3D(-na1000000 2.europe.pool.ntp.org)
term%=20

I'm not sure what the rm was for, but it's not needed now. It must have =
been a debug option. I think I remember timesync complaining if /sys/log=
/timesync existed when it started up.