Information
ID: 50
PHID: PHID-TASK-e225wlkovfhcuv7rvchl
Author: JasonJAyalaP
Status at Migration Time: resolved
Priority at Migration Time: Normal
Description
bug 1
100 % CPU bug:
- [REOPENED] sclockadj stuck at 100% CPU - #26 by Patrick
- 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:
Forum discussion:
https://forums.whonix.org/t/sclockadj2-slow-clock-adjuster-prevent-fingerprintable-clock-adjustments
Related:
T621
Deprecated:
Patrick asked on stackexchange:
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
Comments
Patrick
2018-07-25 06:35:01 UTC