Re: [chrony-users] Request: Add an optional timeout option for 'chronyd -q ...'

2016-12-02 Thread Miroslav Lichvar
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. >

Re: [chrony-users] Request: Add an optional timeout option for 'chronyd -q ...'

2016-12-02 Thread Miroslav Lichvar
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

Re: [chrony-users] Request: Add an optional timeout option for 'chronyd -q ...'

2016-12-02 Thread Lonnie Abelbeck
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