Thanks for the heads up. It sound like ntp_monitor.py won't work on the
embedded board until I close that ticket. Patches are always welcome.
Kevin
On Wed, May 5, 2010 at 12:13 PM, Blaise Gassend <
blaise@willowgarage.com>wrote:
> You will definitely want to use the initstepslew option in your chrony
> configuration.
>
> On Wed, 2010-05-05 at 12:00 -0700, Enea Scioni wrote:
> > Yes, infact embedded board doesn't have a button battery, so every reboot
> > means that the date will reset on 1 Jan 1970: for that reason the offset
> is
> > very high. I'll try chrony to fix this, and I let's you know the result.
> >
> > The output it's the same, both IP and Hostname:
> > 5 May 20:55:46 ntpdate[1558]: no server suitable for synchronization
> found
> >
> > The problem is not the Hostname; before I posted the command using the
> IP,
> > but the behaviour it's always the same.
> > (I checked also /etc/hosts )
> >
> > Enea Scioni
>
>
> _______________________________________________
> ros-users mailing list
> ros-users@code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users
>
(text/plain)