Hi Pedro, worth a discussion for sure, but this was chosen as the default because it is also the same in Debian and more important in the upstream project itself.
See example configs: $ grep makestep examples/chrony.conf.example* examples/chrony.conf.example1:makestep 1.0 3 examples/chrony.conf.example2:makestep 1.0 3 examples/chrony.conf.example3:! makestep 1.0 3 They all have makestep (well the latter is explaining how to comment out things, but anyway). I understand your argument, but vice versa there always is the crowd of "this never gets into sync, so at least on start please step it as so many local clocks are really bad". I'll subscribe Paul who is much more of an NTP expert than I am. But actually I'd ask you to start the discussion on the chrony mailing list. => https://chrony.tuxfamily.org/lists.html There more NTP-focused and experienced people will be around. If it really should be disabled by default then I'd want to see it discussed/decided there and the defaults in the examples changed. Marking incomplete until further discussion happened with Paul and Upstream. Please report back with e.g. a link to the upstream discussion. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778141 Title: chrony will by default step the clock instead of drifting it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1778141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
