* [9fans] aux/timesync -n doesn't work
@ 2019-09-10 14:20 Олег Бахарев
2019-09-10 15:53 ` Richard Miller
` (2 more replies)
0 siblings, 3 replies; 10+ messages in thread
From: Олег Бахарев @ 2019-09-10 14:20 UTC (permalink / raw)
To: Fans of the OS Plan 9 from Bell Labs
[-- Attachment #1: Type: text/plain, Size: 71 bytes --]
aux/timesync doesnt work in raspberry pi 2. How to fix this problem ?
[-- Attachment #2: Type: text/html, Size: 93 bytes --]
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [9fans] aux/timesync -n doesn't work
2019-09-10 14:20 [9fans] aux/timesync -n doesn't work Олег Бахарев
@ 2019-09-10 15:53 ` Richard Miller
2019-09-10 22:40 ` Олег Бахарев
2019-09-11 4:01 ` Ori Bernstein
2019-09-18 18:14 ` Ethan Gardener
2 siblings, 1 reply; 10+ messages in thread
From: Richard Miller @ 2019-09-10 15:53 UTC (permalink / raw)
To: 9fans
> aux/timesync doesnt work in raspberry pi 2
What ntp server are you naming in the timesync -n command?
Can you ip/ping it?
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [9fans] aux/timesync -n doesn't work
2019-09-10 14:20 [9fans] aux/timesync -n doesn't work Олег Бахарев
2019-09-10 15:53 ` Richard Miller
@ 2019-09-11 4:01 ` Ori Bernstein
2019-09-18 18:14 ` Ethan Gardener
2 siblings, 0 replies; 10+ messages in thread
From: Ori Bernstein @ 2019-09-11 4:01 UTC (permalink / raw)
To: Fans of the OS Plan 9 from Bell Labs
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
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [9fans] aux/timesync -n doesn't work
2019-09-10 14:20 [9fans] aux/timesync -n doesn't work Олег Бахарев
2019-09-10 15:53 ` Richard Miller
2019-09-11 4:01 ` Ori Bernstein
@ 2019-09-18 18:14 ` Ethan Gardener
2019-09-19 10:11 ` Richard Miller
2 siblings, 1 reply; 10+ messages in thread
From: Ethan Gardener @ 2019-09-18 18:14 UTC (permalink / raw)
To: 9fans
On Tue, Sep 10, 2019, at 3:20 PM, Олег Бахарев 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=(-na1000000 2.europe.pool.ntp.org)
term%
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.
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [9fans] aux/timesync -n doesn't work
2019-09-18 18:14 ` Ethan Gardener
@ 2019-09-19 10:11 ` Richard Miller
2019-09-22 9:20 ` Ethan Gardener
0 siblings, 1 reply; 10+ messages in thread
From: Richard Miller @ 2019-09-19 10:11 UTC (permalink / raw)
To: 9fans
> # 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.
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [9fans] aux/timesync -n doesn't work
2019-09-19 10:11 ` Richard Miller
@ 2019-09-22 9:20 ` Ethan Gardener
2019-09-22 10:01 ` Richard Miller
0 siblings, 1 reply; 10+ messages in thread
From: Ethan Gardener @ 2019-09-22 9:20 UTC (permalink / raw)
To: 9fans
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.
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [9fans] aux/timesync -n doesn't work
2019-09-22 9:20 ` Ethan Gardener
@ 2019-09-22 10:01 ` Richard Miller
2019-09-28 18:08 ` Ethan Gardener
0 siblings, 1 reply; 10+ messages in thread
From: Richard Miller @ 2019-09-22 10:01 UTC (permalink / raw)
To: 9fans
> 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.
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [9fans] aux/timesync -n doesn't work
2019-09-22 10:01 ` Richard Miller
@ 2019-09-28 18:08 ` Ethan Gardener
0 siblings, 0 replies; 10+ messages in thread
From: Ethan Gardener @ 2019-09-28 18:08 UTC (permalink / raw)
To: 9fans
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.
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2019-09-28 18:08 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-09-10 14:20 [9fans] aux/timesync -n doesn't work Олег Бахарев
2019-09-10 15:53 ` Richard Miller
2019-09-10 22:40 ` Олег Бахарев
2019-09-10 22:53 ` Bakul Shah
2019-09-11 4:01 ` Ori Bernstein
2019-09-18 18:14 ` Ethan Gardener
2019-09-19 10:11 ` Richard Miller
2019-09-22 9:20 ` Ethan Gardener
2019-09-22 10:01 ` Richard Miller
2019-09-28 18:08 ` Ethan Gardener
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).