barto
September 23, 2025, 9:07am
1
[ I don’t intend to report this on github due to lack of an account and moral objections etc. ]
In my R4.2.4 dom0:
[user@dom0 ~]$ cat /etc/cron.d/qubes-sync-clock.cron
0 */1 * * * root /usr/bin/qvm-sync-clock > /dev/null 2>&1 || true
The “*/1” is useless and just obfuscating the simple fact that the script is run every hour at :00.
The file is part of qubes-core-dom0-linux rpm, at least as of version 4.2.36 with “Build Date : Wed 16 Jul 2025 02:00:00 CEST”.
Please fix (with low priority)
5 Likes
parulin
December 19, 2025, 5:35am
3
@barto I bookmarked your topic to create the following issue on Github, but then I read your moral objection… So, is it okay for me to post this on Github?
Qubes OS release
R4.2, R4.3
Brief summary
/etc/cron.d/qubes-sync-clock.cron has an useless value, obfuscating the simple fact that the script is run every hour at :00
Steps to reproduce
Look at the content of the file:
[user@dom0 ~]$ cat /etc/cron.d/qubes-sync-clock.cron
Expected behavior
[user@dom0 ~]$ cat /etc/cron.d/qubes-sync-clock.cron
0 * * * * root /usr/bin/qvm-sync-clock > /dev/null 2>&1 || true
Actual behavior
[user@dom0 ~]$ cat /etc/cron.d/qubes-sync-clock.cron
0 */1 * * * root /usr/bin/qvm-sync-clock > /dev/null 2>&1 || true
Additional information
Minor bug / low priority
From the forum: R4.2 Minor/cosmetic error in qubes-core-dom0-linux
2 Likes
barto
December 20, 2025, 11:26pm
4
Sure, no worries! Appreciated.
2 Likes
