Re: nts and ntske log files

2023-08-28 Thread Hal Murray via devel
>Expires February 2036 minus the current date >is about 12 years and 5 months maybe ish... The context is a duration of time rather than time of day. eg the result of sub_tspec() How many seconds did it take to do X? The current date has nothing to do with it. -- These are my op

Re: nts and ntske log files

2023-08-28 Thread James Browning via devel
On Aug 28, 2023 18:10, James Browning wrote:On Aug 28, 2023 17:10, Hal Murray wrote: James Browning said: > The NTP solution would be to convert the mess to l_fp which > will work for a bit less than 13 years. Thanks.  l_fp is the right answer. How did you get 13 years?  I get 136.  Did

Re: nts and ntske log files

2023-08-28 Thread Hal Murray via devel
James Browning said: > The NTP solution would be to convert the mess to l_fp which > will work for a bit less than 13 years. Thanks. l_fp is the right answer. How did you get 13 years? I get 136. Did you drop/typo the 6? > My joke would be to have it as a long long of micro-seconds which w

Re: nts and ntske log files

2023-08-28 Thread James Browning via devel
> On 08/28/2023 3:08 PM PDT Hal Murray via devel wrote: > > > I just pushed the first cut. > > No documentation yet. > > Like sysstats and usestats, ntsstats and ntskestats get logged every hour. > > If you look at the output from ntpq -c nts, the counters fall into two > clumps, > one for

nts and ntske log files

2023-08-28 Thread Hal Murray via devel
I just pushed the first cut. No documentation yet. Like sysstats and usestats, ntsstats and ntskestats get logged every hour. If you look at the output from ntpq -c nts, the counters fall into two clumps, one for NTS and one for NTS-KE. All the counters get logged in the same order. Should