Is anybody using/testing the interface options?
There is an option in the config file and more on the command line. -- These are my opinions. I hate spam. ___ devel mailing list devel@ntpsec.org https://lists.ntpsec.org/mailman/listinfo/devel
Re: Hack for monitoring NTP servers
James Browning said:
> If you were thinking of adding way too many servers you might want to replace
> the bubble sort around lines 1709-1728 of ntp_proto.c
That code is only sorting the servers that get used. Anything with noselect
got tossed back at line 1619.
if (peer_unfit(peer)) {
continue;
--
These are my opinions. I hate spam.
___
devel mailing list
devel@ntpsec.org
https://lists.ntpsec.org/mailman/listinfo/devel
Re: Hack for monitoring NTP servers
> On 04/11/2024 12:39 PM PDT Hal Murray via devel wrote: > > > If somebody feels like hacking, something like this should be fun. > > The idea is to setup a ntpd server watching the servers you want to monitor. > (noselect on the server line does that) > > The new code is a program that watches that server to see if the servers to > be > monitored are responding correctly and sends you email if they aren't. If you were thinking of adding way too many servers you might want to replace the bubble sort around lines 1709-1728 of ntp_proto.c I would not write such a thing as it would get me banned from Google. ___ devel mailing list devel@ntpsec.org https://lists.ntpsec.org/mailman/listinfo/devel
Re: CI is broken
> On 04/15/2024 9:15 AM PDT Matt Selsky via devel wrote: > > On Sun, Apr 14, 2024 at 01:30:47AM -0700, Hal Murray via devel wrote: > > I just pushed some code. The CI stuff sent me a Failed pipeline message. > > > > > > [0K[31;1mERROR: Job failed: failed to pull image > > "registry.gitlab.com/gitlab-or > > g/gitlab-runner/gitlab-runner-helper:x86_64-v16.11.0" with specified > > policies > > [always]: Error response from daemon: manifest for > > registry.gitlab.com/gitlab-org/gitlab-runner/gitlab-runner-helper:x86_64-v16.11 > > .0 not found: manifest unknown: manifest unknown (manager.go:250:0s) > > > > https://gitlab.com/NTPsec/ntpsec/-/jobs/6619973110/raw > > > > There are 9 copies that looked the same to me. > > Hi Hal, > > I don't see anything on GitLab's status history page at > https://status.gitlab.com/pages/history/5b36dc6502d06804c08349f7 but I expect > there's nothing for us to do and we can just wait for GitLab to fix the > underlying issue (assuming it hasn't been resolved already). It is resolved already. I assume from briefly looking at the logs that it was a new release of the gitlab runner helper that broke it. ___ devel mailing list devel@ntpsec.org https://lists.ntpsec.org/mailman/listinfo/devel
Re: CI is broken
On Sun, Apr 14, 2024 at 01:30:47AM -0700, Hal Murray via devel wrote: > I just pushed some code. The CI stuff sent me a Failed pipeline message. > > > [0K[31;1mERROR: Job failed: failed to pull image > "registry.gitlab.com/gitlab-or > g/gitlab-runner/gitlab-runner-helper:x86_64-v16.11.0" with specified policies > [always]: Error response from daemon: manifest for > registry.gitlab.com/gitlab-org/gitlab-runner/gitlab-runner-helper:x86_64-v16.11 > .0 not found: manifest unknown: manifest unknown (manager.go:250:0s) > > https://gitlab.com/NTPsec/ntpsec/-/jobs/6619973110/raw > > There are 9 copies that looked the same to me. Hi Hal, I don't see anything on GitLab's status history page at https://status.gitlab.com/pages/history/5b36dc6502d06804c08349f7 but I expect there's nothing for us to do and we can just wait for GitLab to fix the underlying issue (assuming it hasn't been resolved already). Thanks, -Matt ___ devel mailing list devel@ntpsec.org https://lists.ntpsec.org/mailman/listinfo/devel
