[chrony-dev] Chrony "Watchdog"

[Harald Krammer <Harald.Krammer@xxxxxx>]

Hello *,
my tests are nearly completed with 1.25. One thing I have noted. 
If a time jump will happen into the past (done by  settimeofday) 
then Chrony  does not update the information's anymore. 
The leap in time happens by a software fault in my application. 
I fixed that, but I have an uneasy feeling. It is clear to me 
that a time-jump is a sensitive subject.

Here you will what's happen:
/ $ date
Fri Apr  8 04:40:10 EST 2011   -> My time jumps back.

/ $ chronyc -n tracking
Reference ID    : 10.1.2.131 (10.1.2.131)
Stratum         : 3
Ref time (UTC)  : Mon Jun  6 09:09:09 2011
System time     : 0.000000104 seconds fast of NTP time
Frequency       : 35.308 ppm slow
Residual freq   : 0.366 ppm
Skew            : 1.116 ppm
Root delay      : 0.001124 seconds
Root dispersion : -12.712535 seconds
/ $ chronyc -n sources
210 Number of sources = 2
MS Name/IP address Stratum Poll LastRx Last sample
=====================================================
^* 10.1.2.131      2    5   136y    -19us[  -57us] +/- 1830us
^? 10.126.9.245    0    6    10y     +0ns[   +0ns] +/-    0ns

Currently I uses the 'System time' from command tracking to find 
out the current offset. That isn't enough. A watchdog 
functionality may be helpful.  What do you think? 

Nice greetings,
Harald

-- 

Harald Krammer

Mobil +43.(0) 664. 130 59 58
Mail: Harald.Krammer (at) hkr.at


---
To unsubscribe email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "unsubscribe" in the subject.
For help email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "help" in the subject.
Trouble?  Email listmaster@xxxxxxxxxxxxxxxxxxxx.