Don't alter system timekeeping
@laeti-tia is already working on this.
Since Jun 5, 2025.
- Dominant language
- JavaScript
- Stars
- 37
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
Per Doug White at Cal Tech:
We recently upgraded all of our test nodes to Perfsonar 5.1.4. After discovering that tests between some of the nodes were failing we determined it was due to “time” not being synchronized. Further investigation determined that the PerfSonar Installation process (curl -s https://downloads.perfsonar.net/install | sh -s - toolkit) had disabled chronyd. It was enabled and running prior to the install and afterward it was still running but had been disabled. As a result, chronyd would not reload after the next reboot.
We have a simple work-around in place as we just issue a “systemctl enable chronyd” immediately following the the software installation so this is not an urgent matter. We thought we would call it to your attention however, in case this is something that can be addressed in a future release.
The toolkit packaging is running configure_ntpd on install. Given that ntpd is deprecated on every platform we support, I think it's time to get out of the business of dictating what manner of time sync is used or enable to Chrony if there isn't already a site-specific config for it.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.