On Wed, 2 Sep 2015, Dennis Gilmore wrote:
> I would really like to know the use cases where chronyd is
> not sufficient and the problems that people are trying to
> solve.
Don't the reasons include ( as in a IoT unit with only
occasional external network access to a timesource ):
1. avoidance of unnecessary FSCK's due to 'elapsed
time since last check'
2. permitting cacheing, and then cache expiration of
potential reliable nameserver information (needed to
'boot-strap' into reaching a timeserver array)
-- Russ herrold
ps: hi, Dennis -- long time, no see
_______________________________________________
arm mailing list
[email protected]
https://admin.fedoraproject.org/mailman/listinfo/arm
