On Mon, May 12, 2014 at 10:15:05AM +0100, Ed W wrote: > On 28/04/2014 13:06, Miroslav Lichvar wrote: > >A better approach would be to make chronyd step the clock via the > >manual feature. For example: > > > >chronyc -a 'manual on' (or enable it in chrony.conf) > > > >chronyc -a -m 'offline' 'settime 1 month' 'makestep' 'manual reset' > > > >chronyc -a -m 'settime 1 month ago' 'makestep' 'manual reset' 'online' > > > > What about simply killing Chrony, allowing it to write its various > dump files to disk > > Then mess with the clock as you see fit > > Then restart chrony using the option to reload time from the RTC - > this should be identical to the situation when booting so everything > should just come up normally?
Yes, that should work too. The advantage of letting chronyd doing the steps is that it will not lose or invalidate the source stats it has collected (the -r option could be used with restarted chronyd to prevent that if the clock can be stepped back accurately). -- Miroslav Lichvar -- To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org with "unsubscribe" in the subject. For help email chrony-users-requ...@chrony.tuxfamily.org with "help" in the subject. Trouble? Email listmas...@chrony.tuxfamily.org.