diff options
| author | DanTheMediocre <djo@live.nl> | 2022-03-23 19:54:45 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-03-23 20:54:45 +0200 |
| commit | 83e13596cb458eff1591abfa1c67f497153295db (patch) | |
| tree | c4bdef398a2f998f113dd25bec3116975972f2bf /web | |
| parent | 1023c3e196fafcc21c10bf3c3c95b88339b82f1a (diff) | |
Adjust timex.plugin information to be less cryptic (#12495)
Co-authored-by: Ilya Mashchenko <ilya@netdata.cloud>
Co-authored-by: Tina Luedtke <kickoke@users.noreply.github.com>
Diffstat (limited to 'web')
| -rw-r--r-- | web/gui/dashboard_info.js | 5 |
1 files changed, 2 insertions, 3 deletions
diff --git a/web/gui/dashboard_info.js b/web/gui/dashboard_info.js index e5a84cc9c7..f2f68e99f2 100644 --- a/web/gui/dashboard_info.js +++ b/web/gui/dashboard_info.js @@ -1310,9 +1310,8 @@ netdataDashboard.context = { }, 'system.clock_sync_state': { - info:'<p>The system clock synchronization state. '+ - 'It is strongly recommended having the clock in sync with reliable NTP servers. Otherwise, '+ - 'it leads to unpredictable problems. '+ + info:'<p>The system clock synchronization state as provided by the <a href="https://man7.org/linux/man-pages/man2/adjtimex.2.html" target="_blank">ntp_adjtime()</a> system call. '+ + 'An unsynchronized clock may be the result of synchronization issues by the NTP daemon or a hardware clock fault. '+ 'It can take several minutes (usually up to 17) before NTP daemon selects a server to synchronize with. '+ '<p><b>State map</b>: 0 - not synchronized, 1 - synchronized.</p>' }, |