Building cpufreq modules into F16 kernel is it right or wrong?

Adam Jackson ajax at
Tue Oct 18 20:16:41 UTC 2011

On Tue, 2011-10-18 at 22:02 +0300, alekcejk at wrote:

> Both ntpd and chrony can't synchronize time in VM's because of large offset.

False.  From chrony.txt:


4.2.27 makestep

Normally chronyd will cause the system to gradually correct any time
offset, by slowing down or speeding up the clock as required.  In
certain situations, the system clock may be so far adrift that this
slewing process would take a very long time to correct the system clock.

   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).

   This is particularly useful when using reference clocks, because the
`initstepslew' directive (*note initstepslew directive::) works only
with NTP sources.

   An example of the use of this directive is

     makestep 1000 10

   This would step system clock if the adjustment is larger than 1000
seconds, but only in the first ten clock updates.


- ajax
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
Url : 

More information about the devel mailing list