chrony: fix limits of frequency types

The frequency_error value is in parts per million and the range of
<-2,2> is too small to cover most computer clocks. The clock_skew_ppm
cannot be negative, but it can also be much larger.

diff --git a/src/types.db b/src/types.db
index 68551875f2b3938cc1d8a1cd8c5539c473f6b545..4a4f56f77eda11d762c00bd005746be35ee71b96 100644 (file)
--- a/src/types.db
+++ b/src/types.db
@@ -26,7 +26,7 @@ clock_last_meas         value:GAUGE:0:U
 clock_last_update       value:GAUGE:U:U
 clock_mode              value:GAUGE:0:U
 clock_reachability      value:GAUGE:0:U
-clock_skew_ppm          value:GAUGE:-2:2
+clock_skew_ppm          value:GAUGE:0:1000000
 clock_state             value:GAUGE:0:U
 clock_stratum           value:GAUGE:0:U
 compression             uncompressed:DERIVE:0:U, compressed:DERIVE:0:U
@@ -89,7 +89,7 @@ filter_result           value:DERIVE:0:U
 flow                    value:GAUGE:0:U
 fork_rate               value:DERIVE:0:U
 frequency               value:GAUGE:0:U
-frequency_error         value:GAUGE:-2:2 
+frequency_error         value:GAUGE:-1000000:1000000
 frequency_offset        value:GAUGE:-1000000:1000000
 fscache_stat            value:DERIVE:0:U
 gauge                   value:GAUGE:U:U