bug 1
100 % CPU bug:

• https://forums.whonix.org/t/reopened-sclockadj-stuck-at-100-cpu/732/26
• 100% CPU but happens reproducibly after suspend and resume in Qubes-Whonix

bug 2
systemd spams journal due to time changed by sclockadj

AvdN built a sclockadj replacement written in python, but more work is needed:
https://github.com/Whonix/sdwdate/pull/4

Forum discussion:
https://forums.whonix.org/t/sclockadj2-slow-clock-adjuster-prevent-fingerprintable-clock-adjustments

Related:
T621

Deprecated:

Patrick asked on stackexchange:
https://unix.stackexchange.com/questions/166639/how-to-disable-systemds-time-has-been-changed-message-spam-in-systemd-journal

Jason:
The only way I see to avoid systemd spam is to change the logging level in the conf file. How is it that adjtimex changes the clock without a systemd message? Maybe sclockadj can do that.

Migrated from github:
https://github.com/Whonix/Whonix/issues/363