Thank you all for the help!
___
devel mailing list
devel@ntpsec.org
https://lists.ntpsec.org/mailman/listinfo/devel
> > > > Lost me. What about sntp do you want to put on gitlab?
> > >
> > > Oh, reading these in reverse order. I think you are offering to
> > > add this as a Merge Request on GitLab? Yes, that would be good.
> >
> > Can I please send the patch via e-mail? I've been struggeling with
> > gitlab
Hi!
> > Lost me. What about sntp do you want to put on gitlab?
>
> Oh, reading these in reverse order. I think you are offering to
> add this as a Merge Request on GitLab? Yes, that would be good.
Can I please send the patch via e-mail? I've been struggeling with
gitlab for an hour and whatev
Just noticed https://ntpsec.org/contributor.html
If you people want to include it, I'll put it in gitlab.
> Hello,
>
> I would like to suggest the following small tweak for the sntp program:
>
> --- sorg 2023-01-02 14:45:52.975926908 +0100
> +++ /usr/bin/sntp 2023-01-02 14:44:13.3226914
Hello,
I would like to suggest the following small tweak for the sntp program:
--- sorg2023-01-02 14:45:52.975926908 +0100
+++ /usr/bin/sntp 2023-01-02 14:44:13.322691440 +0100
@@ -216,12 +216,12 @@
if json:
say('{"time":"%sT%s%s","offset":%f,"precision":%f,"host":"%
> 1. We have at least two people who are expert Go programmers - Ian and
> myself. We have nobody, AFAIK, who is up to speed on Rust. Moving
> the code will be a large amount of work - I don't think any good
> purpose is siolved by adding "learn to be fluent in an entire new
> language" on top of
> > > I've resolved all the Coverity warbings except a new one, "risky
> > > function" related to random(3)/ The supression cookie for that one
> > > is not suppressing; I've sent a requesr to Synopsis about tis.
> >
> > Is ntpsec also checked by 'lgtm.com'? They also do all kinds of
> > verifica
> I've resolved all the Coverity warbings except a new one, "risky
> function" related to random(3)/ The supression cookie for that one
> is not suppressing; I've sent a requesr to Synopsis about tis.
Is ntpsec also checked by 'lgtm.com'? They also do all kinds of
verifications on source-code.
Hi,
/usr/bin/ntpdig -j -p 8
produces an invalid json string:
{"time":"2020-08-29T12:37:41.817391-0200","offset":-0.34,"precision":0.000158,"host":"localhost",ip:"::1","stratum":1,"leap":"no-leap","adjusted":false}
As you can see here, the " before ip: is missing and also the 2nd " is
misplac
> > udo...@xs4all.nl said:
> >> Started things this way. One gdb line worries me a bit: (No debugging
> >> symbols
> >> found in build/main/ntpd/ntpd)
> >
> >> Perhaps a different build is needed?
> >
> > I'm not sure how that stuff works.
> >
> > configure has an --enable-debug-gdb option. T
Hi,
I created a gps-interface. This clock ticks every 2 seconds sometimes 3, 4 of
13 seconds.
Not very reliable but very precise (as it is a contraption connected to a gps).
After it ran for an hour or so, I looked at the output of ntpmon:
remote refid st t when poll reach
> > Can I concatenate the loopstats-files to get statistics over longer time? Or
> > is there some catch?
>
> Sure. The first 2 columns are MJD and seconds-in-day.
Oh and I now realise why it (the octave script for the allan devication)
started to fail; older loopstart-files are gzipped!
__
Hi,
Can I concatenate the loopstats-files to get statistics over longer
time? Or is there some catch?
regards
___
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.org/mailman/listinfo/devel
Hi,
> > Has the format of the loopstats-file changed since the "original ntp"?
>
> I don't remember any changes in that area. We might have fixed (or broken)
> something that rippled out to that file but I don't remember anything like
> that.
>
> If you just plot the raw data (without doing a
Hi,
Has the format of the loopstats-file changed since the "original ntp"?
Because the octave script I used to plot an Allan variance plot no
longer works (altough it has been a few years since I last did that).
http://www.wraith.sf.ca.us/ntp/allan.oct
Folkert van Heusden
--
Hi,
Tried to create a pull-request via gitlab but that failed in mysterious
ways. So that's why I'm also sending it via the mailinglist (I talked
about it on irc as well).
>From a7288a0692f2862590e9b1eea1f05ae8d87a1ff1 Mon Sep 17 00:00:00 2001
From: Folkert van Heusden
Date: Mon, 23 Sep 2019 09
16 matches
Mail list logo
