In the meantime, I tried to see which file runs /lib/systemd/systemd-timesyncd:
# file /lib/systemd/systemd-timesyncd
… interpreter /lib64/ld-linux-x86-64.so.2 …
So I took a look at its directory:
# ls -la /lib64
… /lib64 -> usr/lib64
# ls -la /usr/lib64
drw------ 3 root root 4096 22. Jul 17:23 .
…
I thought, someone else than root might try to execute whatever is inside there
and went on with
# chmod +rx /usr/lib64
so that I got
drwr-xr-x 3 root root 4096 22. Jul 17:23 .
This solved the problem at least once:
# systemctl restart systemd-timesyncd
worked now:
# systemctl status systemd-timesyncd
…
Active: active (running) …
…
I'm absolutely sure I had NOT altered the permissions of /usr/lib64 or any
other system directories myself before having issued the aforementioned chmod
command today at all, so some part of or the system or of the upgrade from
Debian 11 to Debian 12 must have set the directory persmissions to drw------
(presumably, for a good reason?). Are the new permissions drwr-xr-x fine? If
they are normal, is there anything else I need to do? If they are too
permissive, should I change them back and still run strace on
/lib/systemd/systemd-timesyncd (and if not, what else to do)?
Gratefully,
Alma
