Re: [chrony-dev] new feature request: add "fast" and "slow" to "clock wrong" and "clock stepped" log messages

[FUSTE Emmanuel <emmanuel.fuste@xxxxxxxxxxxxxxx>]

Le 30/10/2017 à 19:42, Denny Page a écrit :
> FWIW, I believe “ahead” and “behind” are the most clear in speaking to the condition before initiating a correct. “Fast” and “Slow” somewhat imply an ongoing condition that may or may not be true. It could be the accuracy of setting the RTC before reboot for instance.
>
>      System clock ahead by ?.????????
>      System clock behind by ?.????????
>
> Denny
>
I second you:

For system logs messages
"ahead" / "behind" for offset
"fast" / "slow" for freq

measurements.log are already totally unambiguous/perfectly specified.

Emmanuel.
>> On Oct 30, 2017, at 04:07, Miroslav Lichvar <mlichvar@xxxxxxxxxx> wrote:
>>
>> On Fri, Oct 27, 2017 at 10:31:16AM -0600, James Feeney wrote:
>>> How about, rather than using the term "wrong", instead use the terms "fast" and "slow" to describe this quantity "1.693005 seconds"?  Then the log message might read:
>>>
>>> chronyd[622]: System clock fast by 1.693005 seconds, adjustment started
>>>
>>> or
>>>
>>> chronyd[622]: System clock slow by 1.693005 seconds, adjustment started
>> I agree this would be much clearer for the user. I never remember
>> which sign is for fast and slow in what context (it's not consistent
>> unfortunately). The trouble is that it would break existing scripts
>> that parse the log and the parsing itself would be more difficult if
>> it had to look for the word "slow" or "fast" instead of the sign. I'm
>> not sure how important that really is.
>>
>> Do you think it would make sense to keep the sign and indicate whether
>> it's fast or slow in parentheses?
>>
>> System clock wrong by +/-?.??????? (slow/fast) ?
>>
>> System clock stepped by +/-?.??????? (forward/backward) ?
>>
>> There are other messages that print an offset, so maybe they could be
>> all changed at once to keep it consistent.
>>
>> What do others think?
>>
>> -- 
>> Miroslav Lichvar
>>
>> -- 
>> To unsubscribe email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "unsubscribe" in the subject.
>> For help email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "help" in the subject.
>> Trouble?  Email listmaster@xxxxxxxxxxxxxxxxxxxx.
>>
>