Thanks Miroslav,
comments inline below.
Il 05/08/2015 10:10, Miroslav Lichvar ha scritto:
On Wed, Aug 05, 2015 at 09:55:29AM +0200, Mauro Condarelli wrote:
Il 05/08/2015 03:12, Bill Unruh ha scritto:
Maybe there is something which puts the system to sleep if it is inactive to a
long time.
On Tue, Aug 04, 2015 at 08:50:16AM -0700, Bill Unruh wrote:
> In this context might there be an option for chrony to take the intial time
> when starting up from the date and time on some file. eg --startfile
>
> If that directive is there then chrony would use the mtime (plus say 60 sec)
>
On Tue, Aug 04, 2015 at 08:35:23PM +0200, Mauro Condarelli wrote:
> / # date -s '2025-01-07'
> Tue Jan 7 00:00:00 CET 2025
>
> Jan 7 00:00:00 ok-cash daemon.warn chronyd[494]: Forward time jump detected!
> Jan 7 00:00:00 ok-cash daemon.info chronyd[494]: Can't synchronise: no
> reachable
Update inline below.
Il 04/08/2015 20:55, Mauro Condarelli ha scritto:
Hi,
Thanks for the answer.
Comments inline below.
Il 04/08/2015 17:50, Bill Unruh ha scritto:
On Tue, 4 Aug 2015, Miroslav Lichvar wrote:
On Mon, Aug 03, 2015 at 10:56:51PM +0200, Mauro Condarelli wrote:
2.
Hi,
Thanks for the answer.
Comments inline below.
Il 04/08/2015 17:50, Bill Unruh ha scritto:
On Tue, 4 Aug 2015, Miroslav Lichvar wrote:
On Mon, Aug 03, 2015 at 10:56:51PM +0200, Mauro Condarelli wrote:
2. In the above event, after several minutes, chrony announces it is going to
Hi,
Thanks for the answer.
Comments inline below.
Il 04/08/2015 11:00, Miroslav Lichvar ha scritto:
On Mon, Aug 03, 2015 at 10:56:51PM +0200, Mauro Condarelli wrote:
Absolute precision is not a requirement, I can tolerate errors of several
seconds, but I cannot leave clocks to drift and rely
On Mon, Aug 03, 2015 at 10:56:51PM +0200, Mauro Condarelli wrote:
> Absolute precision is not a requirement, I can tolerate errors of several
> seconds, but I cannot leave clocks to drift and rely on manual
> resynchronization.
>
> My current /etc/chrony.conf is:
>
*Background:* I have several embedded devices (arm9) running linux (currently:
3.16.1 / Buildroot 2015.5) that are powered up at random intervals (some may be
up 24/7, but others may be up only a few hours/week); they may or may not be
connected to the Internet (each station is likely to have
