Re: [9fans] aux/timesync -n doesn't work

2019-09-28 Thread Ethan Gardener 
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.

Re: [9fans] aux/timesync -n doesn't work

2019-09-22 Thread Richard Miller 
> 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.

Re: [9fans] aux/timesync -n doesn't work

2019-09-22 Thread Ethan Gardener 
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.

Re: [9fans] aux/timesync -n doesn't work

2019-09-19 Thread Richard Miller 
> # 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.

Re: [9fans] aux/timesync -n doesn't work

2019-09-18 Thread Ethan Gardener 
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=(-na100 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.

Re: [9fans] aux/timesync -n doesn't work

2019-09-10 Thread Ori Bernstein 
On Tue, 10 Sep 2019 17:20:49 +0300,  __ 
 wrote:

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

Can you define what doesn't work?

-- 
Ori Bernstein

Re: [9fans] aux/timesync -n doesn't work

2019-09-10 Thread Bakul Shah 
May be you can try ru.pool.ntp.org. 

> On Sep 10, 2019, at 3:40 PM, Олег Бахарев  wrote:
> 
> I can ping. Russian ntp2 stratix server
> 
> вт, 10 сент. 2019 г., 18:55 Richard Miller <9f...@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?
> 
>

Re: [9fans] aux/timesync -n doesn't work

2019-09-10 Thread Олег Бахарев 
I can ping. Russian ntp2 stratix server

вт, 10 сент. 2019 г., 18:55 Richard Miller <9f...@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?
>
>
>

Re: [9fans] aux/timesync -n doesn't work

2019-09-10 Thread Richard Miller 
> aux/timesync doesnt work in raspberry pi 2

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