i was thinking that perhaps timesync should refuse to run if the
accuracy is unreasonable?
- erik
> I'm running timesync here on a sheevaplug and an openrd-client.
> The invocation was
>
> aux/timesync -s /net -nl -d /sys/log/timesync.d chips time1 time2
>
> 100 µs accuracy seems unlikely; you might try dropping the
> `-a 10' from your invocation.
ah, yes. thanks for the reply. i
I'm running timesync here on a sheevaplug and an openrd-client.
The invocation was
aux/timesync -s /net -nl -d /sys/log/timesync.d chips time1 time2
100 µs accuracy seems unlikely; you might try dropping the
`-a 10' from your invocation.
The kbdq business is almost certainly a result
On Sat Apr 10 04:03:08 EDT 2010, 9...@9netics.com wrote:
> > 1. timesync locks up my machine. i have the latest clock.c
>
> http://groups.google.com/group/comp.os.plan9/msg/07e419734ebf81a5
however, geoff claimed a fix in december.
http://9fans.net/archive/2009/12/164
- erik
> 1. timesync locks up my machine. i have the latest clock.c
http://groups.google.com/group/comp.os.plan9/msg/07e419734ebf81a5
kw; cat /dev/cputype
ARM Marvell 88F6281 A0; arm926ej-s arch v5te rev 2.1 part 131 1200
1. timesync locks up my machine. i have the latest clock.c
i'm using
aux/timesync -nl -d /sys/log/timesync.d -a 10 $timeserver
perhaps there's something wrong with that?
2. initially crashed on
