Your message dated Sun, 11 Dec 2011 17:04:59 +0100
with message-id <[email protected]>
and subject line Closing long fixed bug
has caused the Debian Bug report #195624,
regarding chrony should step the clock above a certain threshold
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
195624: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=195624
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: chrony
Version: 1.19-6
Severity: wishlist
Whenever I use my dvd burner (ide in PIO mode because otherwise
everything crashed) linux seems to loose clock ticks. For chrony that
results in a large drift much larger than what it can slew. Before I
started burning I had perfect time. After burning 4 dvds I now have:
"System time : 2678.641100 seconds slow of NTP time"
Chrony should have a directive to step the clock when the time
difference exceeds a certain limit or when the time needed to slew
the clock back to the right time excceds a limit.
Before I have my clock running way slow for an hour or even days I
rather want chrony to step it.
MfG
Goswin
PS: I know about "initsepslew" but thats only used when starting.
Maybe that could just be changed to apply at runtime too.
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux dual 2.4.20-ac2-dual #1 SMP Tue Apr 15 15:36:20 CEST 2003 i686
Locale: LANG=C, LC_CTYPE=de_DE
Versions of packages chrony depends on:
ii libc6 2.3.1-16 GNU C Library: Shared libraries an
ii libncurses5 5.3.20021109-2 Shared libraries for terminal hand
ii libreadline4 4.3-4 GNU readline and history libraries
-- no debconf information
--- End Message ---
--- Begin Message ---
makestep:
This directive forces `chronyd' to step system clock if the
adjustment is larger than a threshold value, but only if there were no
more clock updates since `chronyd' was started than a specified limit
(a negative value can be used to disable the limit).
That implements exactly what i asked for:
makestep 1000 -1
--- End Message ---
