> But you could have installed a new chronyc and chronyd, but not then
> restarted
> chronyd, so it is still an old version of chronyd running.

The chrony install was fresh, also, removing the packet definitely also
kills the process.

Funny thing I just saw on my home machine: here, chronyd is running as
"_chrony" user, and as far as I remember, on the work computer it's run as
root. Could that be a potential error?

Reply via email to