We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I can't seem to get that to work. I get the following error when trying to enable tempcomp:
chronyd[79733]: Fatal error : Could not read tempcomp point from /etc/chrony/chrony.tempcomp
I tried playing with the permissions but no luck. System information below:
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)" NAME="Debian GNU/Linux" VERSION_ID="12" VERSION="12 (bookworm)" VERSION_CODENAME=bookworm ID=debian Model : Raspberry Pi 3 Model B Plus Rev 1.3 Linux gps-pi 6.6.31+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.6.31-1+rpt1 (2024-05-29) aarch64 GNU/Linux
Thanks for your great work!
The text was updated successfully, but these errors were encountered:
@phipac , paste here the result of the command:
ls -la /etc/chrony/chrony.tempcomp
It should be similar to:
-rw-r--r-- 1 root root 88 Jan 5 20:30 /etc/chrony/chrony.tempcomp
Sorry, something went wrong.
@tiagofreire-pt
$ ls -la /etc/chrony/chrony.tempcomp -rwxrwxrwx 1 root root 89 Jun 12 16:14 /etc/chrony/chrony.tempcomp
No branches or pull requests
I can't seem to get that to work. I get the following error when trying to enable tempcomp:
chronyd[79733]: Fatal error : Could not read tempcomp point from /etc/chrony/chrony.tempcomp
I tried playing with the permissions but no luck. System information below:
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
Model : Raspberry Pi 3 Model B Plus Rev 1.3
Linux gps-pi 6.6.31+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.6.31-1+rpt1 (2024-05-29) aarch64 GNU/Linux
Thanks for your great work!
The text was updated successfully, but these errors were encountered: