summaryrefslogtreecommitdiff
path: root/meson_options.txt
diff options
context:
space:
mode:
authorFranck Bui <fbui@suse.com>2022-08-23 17:07:23 +0200
committerLuca Boccassi <luca.boccassi@gmail.com>2022-08-24 21:39:46 +0100
commit2306b4656a822e83c2a2563131be8d676c8bfb71 (patch)
tree95285b875076e4224a84360a67f5b7abd3417959 /meson_options.txt
parent34683dbdd019f7e1cf6598d94efce3c0dfe42afe (diff)
downloadsystemd-2306b4656a822e83c2a2563131be8d676c8bfb71.tar.gz
core: allow disabling system time correction if rtc returns time far in the future
There might be (embedded) systems that get never updated (things like e.g. entertainment systems of trains, for example) and where the adjustment of the system clock (introduced by b10abe4bba61aebe4c667c412741193f11886298) would do the wrong thing even if the difference between the systemd build time and the rtc is 15 years or more. This patch allows disabling the adjustment by setting 'clock-valid-range-usec-max' meson option to 0 or to a negative value.
Diffstat (limited to 'meson_options.txt')
-rw-r--r--meson_options.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/meson_options.txt b/meson_options.txt
index d5237f02ae..814f340840 100644
--- a/meson_options.txt
+++ b/meson_options.txt
@@ -223,7 +223,7 @@ option('status-unit-format-default', type : 'combo',
option('time-epoch', type : 'integer', value : 0,
description : 'time epoch for time clients')
option('clock-valid-range-usec-max', type : 'integer', value : 473364000000000, # 15 years
- description : 'maximum value in microseconds for the difference between RTC and epoch, exceeding which is considered an RTC error')
+ description : 'maximum value in microseconds for the difference between RTC and epoch, exceeding which is considered an RTC error ["0" disables]')
option('default-user-shell', type : 'string', value : '/bin/bash',
description : 'default interactive shell')