Hi Miroslav, (comments inline)
On Dec 1, 2016, at 5:20 AM, Miroslav Lichvar wrote:
>> Does adding a "-t timeout" option to be used with "chronyd -q ..." sound
>> reasonable ? We would probably use -t 8 (in seconds) for the upper bound.
>
> So you would be ok with chronyd
On Wed, Nov 30, 2016 at 02:01:19PM -0600, Lonnie Abelbeck wrote:
> HI,
>
> We are in the process of moving from 'ntp' to 'chrony' for our open source
> project.
>
> In a matter of a few hours, I have made the conversion, including testing by
> booting without a network connection, restart
On Thu, Dec 01, 2016 at 06:30:22AM -0600, Lonnie Abelbeck wrote:
> Certainly, If a cron job was used to periodically call chronyd instead of
> ntpdate, a "-t timeout_secs" option would be quite useful to make sure a
> stuck/delayed chronyd would not prevent later chronyd's from running.
I'd not
On Dec 1, 2016, at 6:47 AM, Miroslav Lichvar wrote:
> On Thu, Dec 01, 2016 at 06:30:22AM -0600, Lonnie Abelbeck wrote:
>> Certainly, If a cron job was used to periodically call chronyd instead of
>> ntpdate, a "-t timeout_secs" option would be quite useful to make sure a