Thanks Miroslav.
Comments below.
Il 08/08/2016 10:34, Miroslav Lichvar ha scritto:
On Sun, Aug 07, 2016 at 05:06:46AM +0200, Mauro Condarelli wrote:
Thanks Steve.
I know about "chronyc tracking", but that is human-readable info.
I need to parse it (in a shell script) to delay star
om the time of your servers
UTC. I usually set my clocks in the bios to utc, or very close and chrony will use this
as a starting point after boot.
On Aug 6, 2016 12:11 PM, "Mauro Condarelli" <mc5...@mclink.it
<mailto:mc5...@mclink.it>> wrote:
Hi,
I need to star
Hi,
I need to start an application with stable and confirmed date, i.e.: after
chrony has started, initialized and set the system clock to some presumably valid
value.
Since I am using clock skewing if system time is in the future (need strictly
monotonic time), internet connection may be
Thanks a lot,
comments below.
Il 14/04/2016 23:03, Bill Unruh ha scritto:
...snip...
With no rtc ( which is a hardware problem not a chrony problem) there is no
way the system can know what the time is or how to make sure everything is
always monotonic. You will just have to make sure that
Thanks.
Is it advised to move to latest version?
... or should I stick to the current one (1.31)?
TiA
Mauro
Il 19/11/2015 02:16, Bill Unruh ha scritto:
On Thu, 19 Nov 2015, Mauro Condarelli wrote:
Thanks Bill,
now I am getting somewhere (at least chronyc seems to work).
I am still very
generatecommandkey
#makestep 1.0 3
maxupdateskew 100.0
dumponexit
dumpdir /var/lib/chrony
rtconutc
rtcautotrim 1
rtcfile /var/lib/chrony/rtc
#bindcmdaddress /var/run/chronyd.sock
/ #
What am I doing wrong?
Il 19/11/2015 00:31, Bill Unruh ha scritto:
On Thu, 19 Nov 2015, Mauro Condarelli wrote:
Hi Bill
| www.theory.physics.ubc.ca/
On Wed, 18 Nov 2015, Mauro Condarelli wrote:
Thanks Bill,
comments inline below.
Il 18/11/2015 20:40, Bill Unruh ha scritto:
Unfortunately something is seriously wrong:
I get consistently "506 Cannot talk to daemon" to each and all chronyc commands
I try (while
Hi Bill,
comments inline below.
Il 18/11/2015 21:04, Bill Unruh ha scritto:
On Wed, 18 Nov 2015, Mauro Condarelli wrote:
Thanks Bill,
comments inline below.
Il 18/11/2015 20:40, Bill Unruh ha scritto:
Unfortunately something is seriously wrong:
I get consistently "506 Cannot
1160
unix 2 [ ] DGRAM 1208
unix 2 [ ] DGRAM 662
What should I check?
Il 18/11/2015 14:03, Miroslav Lichvar ha scritto:
On Wed, Nov 18, 2015 at 01:39:40PM +0100, Mauro Condarelli wrote:
4) wait for network to go up
5) sync t
Thanks Miroslav,
comments are inline below.
Il 18/11/2015 11:33, Miroslav Lichvar ha scritto:
On Wed, Nov 18, 2015 at 12:04:07AM +0100, Mauro Condarelli wrote:
I have an embedded system (ARM9/Buildroot) that may or may not be connected to the
Internet (usually it is, but it should work also
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
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
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
*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
15 matches
Mail list logo