On Wed, Sep 02, 2015 at 09:29:27AM -0500, Dennis Gilmore wrote: > any attempt to set the time based on something in the filesystem is going to > result in the time being off. if it is something baked in at compose or image > creation time the drift will get bigger over time. if it is some service that > sets it on shutdown the drift will be small. network is required to get it > accurate. > > I would really like to know the use cases where chronyd is not sufficient and > the problems that people are trying to solve. I think the purpose of saving and restoring system time from a file is to have monotonic time on machines that don't have a network connection or only have an intermittent connection, so messages in logs can be sorted, make doesn't complain timestamps are in future, etc. -- Miroslav Lichvar _______________________________________________ arm mailing list arm@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/arm
