On Fri, Dec 02, 2016 at 09:32:35AM -0600, Lonnie Abelbeck wrote:
> On Dec 2, 2016, at 7:57 AM, Miroslav Lichvar wrote:
> > The -t option is now in git. If you test it, please let me know if it
> > works for you as expected.
>
> Works perfectly !
Great.
> You will want to
On Dec 2, 2016, at 7:57 AM, Miroslav Lichvar wrote:
> On Thu, Dec 01, 2016 at 07:07:53AM -0600, Lonnie Abelbeck wrote:
>>> How about returning 0 if the clock was in a synchronised state (the
>>> reference was updated at least once) and 1 if not? With -q that would
>>> be 0
On Thu, Dec 01, 2016 at 07:07:53AM -0600, Lonnie Abelbeck wrote:
> > How about returning 0 if the clock was in a synchronised state (the
> > reference was updated at least once) and 1 if not? With -q that would
> > be 0 only if the clock was stepped.
>
> Yes, that would work for our situation.
>
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
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
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
The problem with stress testing is it can become like throwing a beer bottle
at a concrete wall. It was never intended to survive.
But I guess you could argue that chrony should not freeze if it gets a KoD.
Hoeever you should never be running it so you get a KoD. It is an extreme
response of a
On Wed, 30 Nov 2016, 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 chrony every 10 seconds for a
100+
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 chrony every 10 seconds for a
100+ times, etc .
I am very impressed with 'chrony'
10 matches
Mail list logo