From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
From: =?UTF-8?B?0J7Qu9C10LMg0JHQsNGF0LDRgNC10LI=?= <disconnectix@gmail.com>
Date: Tue, 10 Sep 2019 17:20:49 +0300
Message-ID: <CALp9=o+xMY-LWpL98BB4vmQpCO1sjMcDtqzAtpb+vK3xFm+58g@mail.gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: multipart/alternative; boundary="000000000000a42fac0592339d18"
Subject: [9fans] aux/timesync -n doesn't work
Topicbox-Message-UUID: 076af484-eada-11e9-9d60-3106f5b1d025

--000000000000a42fac0592339d18
Content-Type: text/plain; charset="UTF-8"

aux/timesync doesnt work in raspberry pi 2. How to fix this problem ?

--000000000000a42fac0592339d18
Content-Type: text/html; charset="UTF-8"

<div dir="auto">aux/timesync doesnt work in raspberry pi 2. How to fix this problem ?</div>

--000000000000a42fac0592339d18--



From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <dc691ecc33a3dfe5e9b8d9ae31155f42@hamnavoe.com>
To: 9fans@9fans.net
From: Richard Miller <9fans@hamnavoe.com>
Date: Tue, 10 Sep 2019 16:53:23 +0100
In-Reply-To: <CALp9=o+xMY-LWpL98BB4vmQpCO1sjMcDtqzAtpb+vK3xFm+58g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] aux/timesync -n doesn't work
Topicbox-Message-UUID: 0781798e-eada-11e9-9d60-3106f5b1d025

> aux/timesync doesnt work in raspberry pi 2

What ntp server are you naming in the timesync -n command?
Can you ip/ping it?




From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
References: <CALp9=o+xMY-LWpL98BB4vmQpCO1sjMcDtqzAtpb+vK3xFm+58g@mail.gmail.com>
	<dc691ecc33a3dfe5e9b8d9ae31155f42@hamnavoe.com>
In-Reply-To: <dc691ecc33a3dfe5e9b8d9ae31155f42@hamnavoe.com>
From: =?UTF-8?B?0J7Qu9C10LMg0JHQsNGF0LDRgNC10LI=?= <disconnectix@gmail.com>
Date: Wed, 11 Sep 2019 01:40:46 +0300
Message-ID: <CALp9=o+1xfrd93Y2Soy5qivTMihydthFhZ9OXB=-F5fB29KNeA@mail.gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: multipart/alternative; boundary="00000000000052661205923a99c4"
Subject: Re: [9fans] aux/timesync -n doesn't work
Topicbox-Message-UUID: 078ddbc0-eada-11e9-9d60-3106f5b1d025

--00000000000052661205923a99c4
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

I can ping. Russian ntp2 stratix server

=D0=B2=D1=82, 10 =D1=81=D0=B5=D0=BD=D1=82. 2019 =D0=B3., 18:55 Richard Mill=
er <9fans@hamnavoe.com>:

> > aux/timesync doesnt work in raspberry pi 2
>
> What ntp server are you naming in the timesync -n command?
> Can you ip/ping it?
>
>
>

--00000000000052661205923a99c4
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">I can ping. Russian ntp2 stratix server</div><br><div cla=
ss=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">=D0=B2=D1=82, 10 =
=D1=81=D0=B5=D0=BD=D1=82. 2019 =D0=B3., 18:55 Richard Miller &lt;<a href=3D=
"mailto:9fans@hamnavoe.com">9fans@hamnavoe.com</a>&gt;:<br></div><blockquot=
e class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc sol=
id;padding-left:1ex">&gt; aux/timesync doesnt work in raspberry pi 2<br>
<br>
What ntp server are you naming in the timesync -n command?<br>
Can you ip/ping it?<br>
<br>
<br>
</blockquote></div>

--00000000000052661205923a99c4--



From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bakul Shah <bakul@bitblocks.com>
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_C2B48F4C-E442-4CA2-AA8B-02F3190788AA"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Tue, 10 Sep 2019 15:53:26 -0700
References: <CALp9=o+xMY-LWpL98BB4vmQpCO1sjMcDtqzAtpb+vK3xFm+58g@mail.gmail.com>
	<dc691ecc33a3dfe5e9b8d9ae31155f42@hamnavoe.com>
	<CALp9=o+1xfrd93Y2Soy5qivTMihydthFhZ9OXB=-F5fB29KNeA@mail.gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
In-Reply-To: <CALp9=o+1xfrd93Y2Soy5qivTMihydthFhZ9OXB=-F5fB29KNeA@mail.gmail.com>
Message-Id: <4996A5E7-9B36-4944-93D3-D7395E04841E@bitblocks.com>
Subject: Re: [9fans] aux/timesync -n doesn't work
Topicbox-Message-UUID: 079426ce-eada-11e9-9d60-3106f5b1d025


--Apple-Mail=_C2B48F4C-E442-4CA2-AA8B-02F3190788AA
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

May be you can try ru.pool.ntp.org.=20

> On Sep 10, 2019, at 3:40 PM, =D0=9E=D0=BB=D0=B5=D0=B3 =D0=91=D0=B0=D1=85=
=D0=B0=D1=80=D0=B5=D0=B2 <disconnectix@gmail.com> wrote:
>=20
> I can ping. Russian ntp2 stratix server
>=20
> =D0=B2=D1=82, 10 =D1=81=D0=B5=D0=BD=D1=82. 2019 =D0=B3., 18:55 Richard =
Miller <9fans@hamnavoe.com <mailto:9fans@hamnavoe.com>>:
> > aux/timesync doesnt work in raspberry pi 2
>=20
> What ntp server are you naming in the timesync -n command?
> Can you ip/ping it?
>=20
>=20


--Apple-Mail=_C2B48F4C-E442-4CA2-AA8B-02F3190788AA
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">May =
be you can try <a href=3D"http://ru.pool.ntp.org" =
class=3D"">ru.pool.ntp.org</a>.&nbsp;<br class=3D""><div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D"">On Sep =
10, 2019, at 3:40 PM, =D0=9E=D0=BB=D0=B5=D0=B3 =D0=91=D0=B0=D1=85=D0=B0=D1=
=80=D0=B5=D0=B2 &lt;<a href=3D"mailto:disconnectix@gmail.com" =
class=3D"">disconnectix@gmail.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div dir=3D"auto" =
class=3D"">I can ping. Russian ntp2 stratix server</div><br =
class=3D""><div class=3D"gmail_quote"><div dir=3D"ltr" =
class=3D"gmail_attr">=D0=B2=D1=82, 10 =D1=81=D0=B5=D0=BD=D1=82. 2019 =
=D0=B3., 18:55 Richard Miller &lt;<a href=3D"mailto:9fans@hamnavoe.com" =
class=3D"">9fans@hamnavoe.com</a>&gt;:<br class=3D""></div><blockquote =
class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex">&gt; aux/timesync doesnt work in raspberry pi =
2<br class=3D"">
<br class=3D"">
What ntp server are you naming in the timesync -n command?<br class=3D"">
Can you ip/ping it?<br class=3D"">
<br class=3D"">
<br class=3D"">
</blockquote></div>
</div></blockquote></div><br class=3D""></body></html>=

--Apple-Mail=_C2B48F4C-E442-4CA2-AA8B-02F3190788AA--



From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Tue, 10 Sep 2019 21:01:09 -0700
From: Ori Bernstein <ori@eigenstate.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Message-Id: <20190910210109.fd7c11b01a3b35a3824ced7c@eigenstate.org>
In-Reply-To: <CALp9=o+xMY-LWpL98BB4vmQpCO1sjMcDtqzAtpb+vK3xFm+58g@mail.gmail.com>
References: <CALp9=o+xMY-LWpL98BB4vmQpCO1sjMcDtqzAtpb+vK3xFm+58g@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] aux/timesync -n doesn't work
Topicbox-Message-UUID: 07b34b1c-eada-11e9-9d60-3106f5b1d025

On Tue, 10 Sep 2019 17:20:49 +0300, ________ ______________ <disconnectix@gmail.com> wrote:

> aux/timesync doesnt work in raspberry pi 2. How to fix this problem ?

Can you define what doesn't work?

-- 
    Ori Bernstein



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.



From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <637e049e8df3190ef662c5df247e0e6b@hamnavoe.com>
To: 9fans@9fans.net
From: Richard Miller <9fans@hamnavoe.com>
Date: Thu, 19 Sep 2019 11:11:29 +0100
In-Reply-To: <a8a72f9f-fede-417c-8d9a-49ae3d365e38@www.fastmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] aux/timesync -n doesn't work
Topicbox-Message-UUID: 089668ac-eada-11e9-9d60-3106f5b1d025

> # when timesync(8) says "$ntp", it's lying.

Actually it's not.  But it depends on having a definition
for ntp= associated with your host or [sub]network in the
ndb database.




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: <5b63517d-e907-4b04-8493-7d62c7c8365b@www.fastmail.com>
In-Reply-To: <637e049e8df3190ef662c5df247e0e6b@hamnavoe.com>
References: <637e049e8df3190ef662c5df247e0e6b@hamnavoe.com>
Date: Sun, 22 Sep 2019 10:20:31 +0100
From: "Ethan Gardener" <eekee57@fastmail.fm>
To: 9fans@9fans.net
Content-Type: text/plain
Subject: Re: [9fans] aux/timesync -n doesn't work
Topicbox-Message-UUID: 0a9ce482-eada-11e9-9d60-3106f5b1d025

On Thu, Sep 19, 2019, at 11:11 AM, Richard Miller wrote:
> > # when timesync(8) says "$ntp", it's lying.
> 
> Actually it's not.  But it depends on having a definition
> for ntp= associated with your host or [sub]network in the
> ndb database.

Oh of course! I wrote a top-level definition in ndb, assuming it would be inherited by networks and hosts. I don't think I ever had a reason for that assumption beyond laziness and craziness.



From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <908fbd8be77241caf98991f4b59dc006@hamnavoe.com>
To: 9fans@9fans.net
From: Richard Miller <9fans@hamnavoe.com>
Date: Sun, 22 Sep 2019 11:01:16 +0100
In-Reply-To: <5b63517d-e907-4b04-8493-7d62c7c8365b@www.fastmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] aux/timesync -n doesn't work
Topicbox-Message-UUID: 0ad7ba08-eada-11e9-9d60-3106f5b1d025

> I don't think I ever had a reason for that assumption beyond laziness and craziness.

Not so crazy.  RTFMing in Plan 9 requires close attention - minimalist style
means every word matters.  The clue is in ndb(6):

          Ndb/cs can be made to perform such network aware searches by
          using metanames in the dialstring.  A metaname is a $ fol-
          lowed by an attribute name.  Ndb/cs looks up the attribute
          relative to the system it is running on.




From mboxrd@z Thu Jan  1 00:00:00 1970
User-Agent: Cyrus-JMAP/3.1.7-305-g4111847-fmstable-20190924v1
Mime-Version: 1.0
Message-Id: <06f2e894-3562-4e7e-bdd5-9601b048df57@www.fastmail.com>
In-Reply-To: <908fbd8be77241caf98991f4b59dc006@hamnavoe.com>
References: <908fbd8be77241caf98991f4b59dc006@hamnavoe.com>
Date: Sat, 28 Sep 2019 19:08:12 +0100
From: "Ethan Gardener" <eekee57@fastmail.fm>
To: 9fans@9fans.net
Content-Type: text/plain
Subject: Re: [9fans] aux/timesync -n doesn't work
Topicbox-Message-UUID: 783ccaea-ec36-11e9-914b-36aef4b1d025

On Sun, Sep 22, 2019, at 11:01 AM, Richard Miller wrote:
> > I don't think I ever had a reason for that assumption beyond laziness and craziness.
> 
> Not so crazy.  RTFMing in Plan 9 requires close attention - minimalist style
> means every word matters. 

Thanks!  The trouble is I knew that; 9 or 10 years ago, I was telling other people!  I don't know what happened, but it's been a long time since I wanted to put everything aside and clear my head to just read the instructions.  Hmm... these days, I don't think my mood would let me if I tried.  I think I might be able to fix that.