Yo All!
I'm now getting a lot of this when building git head:
[405/460] Compiling build/main/pylib/__pycache__/agentx_packet.cpython-312.pyo
:1: SyntaxWarning: invalid escape sequence '\S'
:1: SyntaxWarning: invalid escape sequence '\S'
Ideas?
RGDS
GARY
-
Yo Hal!
On Sat, 07 Sep 2024 17:43:32 -0700
Hal Murray via devel wrote:
> James said:
> >It is one of many jobs set up to fail withou fanfare. Nobody was
> >checking up on them on the pipelines tab at GitLab.
>
> Why do we have those jobs?
To test commits that they don't break the bu
Yo James!
On Sat, 07 Sep 2024 10:14:57 -0700
James Browning via devel wrote:
> The Ubuntu 16 04 "cross-build" job is busted and I have no idea how
> to fix it. I thought one idea behind the "build-cross-armhf" job was
> that "cross-build" would have gone away.
I have no idea about Ubuntu or cro
Yo Hal!
On Tue, 06 Aug 2024 17:48:11 -0700
Hal Murray via devel wrote:
> [From https://gitlab.com/NTPsec/ntpsec/-/merge_requests/1399]
>
> Gary said:
>
> > But I agree with you that howto run non-root needs to be
> > documented, and I would also like tests in ntpd to verify the
> > needed CAPS
Yo Hal!
On Wed, 26 Jun 2024 20:32:19 -0700
Hal Murray via devel wrote:
> I'm trying to setup a Pi with a GPS hat.
>
>
>
> The Microserver HOWTO says:
>
> {--config} Edit /boot/config.txt and add these lines to the end of
> the file, replacing 4 with the logical pin number for your HAT if
> i
Yo Richard!
On Fri, 12 Apr 2024 14:12:41 -0500
Richard Laager via devel wrote:
> On 2024-04-11 14:39, 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. (nose
Yo Hal!
On Tue, 05 Dec 2023 20:40:46 -0800
Hal Murray via devel wrote:
> I expect the comment on the previous line to tell Coverity to not
> complain about this case.
>
> Is there a typo or such that I'm missing?
>
> 149/* coverity[checked_return] */
> CID 462307 (#1 of 1): Unchecked
Yo Hal!
On Sun, 03 Dec 2023 17:44:45 -0800
Hal Murray via devel wrote:
> Gary said:
> > DO you have an account on: https://scan.coverity.com/
> > If so, I think I can add you to the project.
>
> How does their stuff work? How often do they check NTPsec?
> Or what should I be asking?
Ever
Yo Hal!
On Sun, 03 Dec 2023 15:07:18 -0800
Hal Murray via devel wrote:
> > Gary said:
> > > Uh, not quite. Check the Coverity stuff.
> >
> > How do I do that?
>
> DO you have an account on: https://scan.coverity.com/
On further checking,halmurray...@sonic.net is an admin
on the
Yo Hal!
On Sun, 03 Dec 2023 15:07:18 -0800
Hal Murray via devel wrote:
> Gary said:
> > Uh, not quite. Check the Coverity stuff.
>
> How do I do that?
DO you have an account on: https://scan.coverity.com/
If so, I think I can add you to the project.
RGDS
GARY
-
Yo James!
On Sat, 2 Dec 2023 21:12:04 -0800 (PST)
James Browning via devel wrote:
> 4. The buildbots are not reporting any unplanned regressions; there
> are always issues to be addressed.
Uh, not quite. Check the Coverity stuff.
RGDS
GARY
-
Yo Hal!
On Thu, 19 Oct 2023 17:45:43 -0700
Hal Murray via devel wrote:
> Found it. systemd sets up separate /tmp for some services.
Yeah, systemd(umb) is your problem...
RGDS
GARY
---
Gary E. Miller Rellim 109 NW Wilmingt
Yo Hal!
On Thu, 19 Oct 2023 14:27:56 -0700
Hal Murray wrote:
> Gary said:
> > Notice the "nodev"?
> > From "man chmod":
> >nodev
> >Do not interpret character or block special devices on
> > the filesystem.
>
> It works fine from my test program. What's different about n
Yo Hal!
On Thu, 19 Oct 2023 13:42:08 -0700
Hal Murray wrote:
> devel@ntpsec.org said:
> > Can you provide:
> > ~ $ ls -ld /tmp drwxrwxrwt 12 root root 580 Oct 19 11:00 /tmp
>
> Changing the owner to ntp didn't make any difference.
Nor would I expect it to.
> > And:
> > ~ $ mount | fgrep /t
Yo Hal!
On Wed, 18 Oct 2023 21:37:06 -0700
Hal Murray via devel wrote:
> What's magic about ntpd and /tmp/?
Many things.
Can you provide:
~ $ ls -ld /tmp
drwxrwxrwt 12 root root 580 Oct 19 11:00 /tmp
And:
~ $ mount | fgrep /tmp
tmpfs on /tmp type tmpfs (rw,nosuid,relatime,size=2097152k)
Yo Hal!
On Tue, 12 Sep 2023 18:49:35 -0700
Hal Murray via devel wrote:
> I think it's worth some effort to investigate this area. I'm
> prepared to give up if we find a fatal problem. Again, I'm assuming
> that we split ntpd into client and server parts so all we have to
> work on is the serve
Yo Hal!
On Tue, 12 Sep 2023 16:55:12 -0700
Hal Murray via devel wrote:
> Gary said:
> >James Browning via devel wrote:
> >> It would appear there is a way to turn off GC under runtime/,
> > How? Link?
>
> https://pkg.go.dev/runtime/debug#SetGCPercent
>
> It's not clear to me how to ta
Yo Hal!
On Tue, 12 Sep 2023 00:00:47 -0700
Hal Murray via devel wrote:
> Gary said:
> > Please, no. Go is a garbage collected language. Just what NTPsec
> > does not need, random, unpredictable delays.
>
> I was thinking of the Python code in ntpclients/ and pylib/
> Is there anything in t
Yo James!
On Tue, 12 Sep 2023 06:46:38 -0700 (PDT)
James Browning via devel wrote:
> > On 09/12/2023 12:00 AM PDT Hal Murray via devel
> > wrote:
> >
> >
> > Gary said:
> > > Please, no. Go is a garbage collected language. Just what
> > > NTPsec does not need, random, unpredictable delay
Yo Hal!
On Mon, 11 Sep 2023 22:03:45 -0700
Hal Murray via devel wrote:
> Maybe it's time to switch to Go?
Please, no. Go is a garbage collected language. Just what NTPsec does
not need, random, unpredictable delays.
RGDS
GARY
--
Yo Richard!
On Mon, 4 Sep 2023 19:24:22 -0500
Richard Laager via devel wrote:
> Dropping support for Python 2 should allow for dropping most of the
> poly infrastructure. That code (pylib/poly.py) involves some
> contortions (see also [1]) to make it possible to run on both Python
> 2 and Python
Yo Matthew!
On Mon, 4 Sep 2023 21:46:50 +
Matthew Selsky wrote:
> Is the implication that we can safely drop python2 support after June
> 2024?
Maybe. RHEL, and friends, are the last to drop things. Worse, people
that use RHEL, and friends, seem to never update their systems...
> Are the
Yo James!
On Mon, 04 Sep 2023 15:38:26 -0700
James Browning via devel wrote:
> > By dropping 2.7 we could probably assume secrets which simplifies
> > ntpkeygen, simplify ntp.poly, be able to drop the now oldoldstable?
> > runner testing for asciidoc on python 2 support, and also have the
> > op
Yo Hal!
On Mon, 04 Sep 2023 15:46:45 -0700
Hal Murray via devel wrote:
> > Rumours of its death are greatly exagerated.
>
> Thanks.
>
> Let me try again with maybe closer to what I should have asked?
>
> Are there any distros that we currently run on that don't support
> python 3?
RHEL.
>
Yo Hal!
On Mon, 04 Sep 2023 14:15:26 -0700
Hal Murray via devel wrote:
> Really really dead? Or maybe just hiding in some dark corner?
Rumours of its death are greatly exagerated.
> Should we drop support for python2 as part of the next release?
> Or announce in the next release that we will
Yo Hal!
On Sun, 23 Jul 2023 18:13:36 -0700
Hal Murray via devel wrote:
> Author: Hal Murray
[...]
> I haven't used that email in ages. My profile has been updated.
It is in you local git config.
> Where is the other address stored and how do I fix it?
Here is how I change it:
git config -
Yo Hal!
On Tue, 20 Jun 2023 12:57:40 -0700
Hal Murray via devel wrote:
> Is anybdy familiar with this area?
> Is this something I did? Or are others seeing the same problem?
> (I might have turned on some more-warnings flag, but I don't think
> so.)
>
> ../../tests/unity/unity.c:984:5: warning
Yo Hal!
On Sat, 03 Jun 2023 21:53:34 -0700
Hal Murray via devel wrote:
> Gary said:
> > To open to read binary:
> > tty = open("/dev/ttyACM0", "rb")
> > The line will be binary. Getting just the NMEA out will be fun.
>
> Thanks. That's what I needed.
Good.
> There is no problem getti
Yo Hal!
On Mon, 29 May 2023 15:22:43 -0700
Hal Murray via devel wrote:
> Can somebody give me a lesson on this area?
>
> The code is:
> tty = open("/dev/ttyACM0")
> forever:
> line = tty.readline()
> a) How do I read mostly ASCII without crashing when there is
> non-ASCII?
To open to
Yo James!
On Tue, 07 Feb 2023 22:54:30 -0800
James Browning via devel wrote:
> > Can you poke it by hand?
> >
> Not as such, no. But it is easy for an authorized user to trigger a
> scheduled run at GitLab. It's under ci > schedules on the left
> sidebar.
The coverity scans are not part of the
Yo Hal!
On Tue, 07 Feb 2023 18:23:17 -0800
Hal Murray via devel wrote:
> Yes, it's reasonably obvious, but only after you find the right URL.
Consider it like a game of Adventure.
> > I approved your account.
>
> Thanks. I didn't get any you-were-approved mail.
>
> Do I have to explicitly
Yo Hal!
On Tue, 07 Feb 2023 14:03:50 -0800
Hal Murray via devel wrote:
> I took a look at the Coverity reports for ntpsec.
> There are 10 of them. 10 is a small number. We should be able to
> fix them all.
Good.
> The Coverity report that started this thread was actually a bug.
My experienc
Yo Hal!
On Tue, 07 Feb 2023 13:20:38 -0800
Hal Murray via devel wrote:
> >> OK, I propose to turn on -Wswitch-enum and fix all the warnings I
> >> find. Then I/we fix whatever Coverity complains about. If that is
> >> too painful, we can back out of -Wswitch-enum.
> > Seems good to me.
>
Yo Hal!
On Mon, 06 Feb 2023 22:51:02 -0800
Hal Murray wrote:
> > I'm waiting for somebody to approve me.
>
> Where? How would I see it?
The request was stuck in my spam folder. Looks like someone beat me
to approving you.
RGDS
GARY
Yo Hal!
On Mon, 06 Feb 2023 22:51:02 -0800
Hal Murray wrote:
> Thanks.
>
> > Do you have a coverity account?
> > https://scan.coverity.com/
> > Then go to "My Dashboard" and "Add project".
>
> Should we document that? Where?
The procedure changes more often than we add cverity users.
> It
Yo Hal!
On Mon, 06 Feb 2023 20:08:21 -0800
Hal Murray wrote:
> >> But then Coverity will barf (DEADCODE) at all the defaults.
> > What purpose do they still have?
>
> None. But we have -Wswitch-default so it will barf if we remove them.
>
> They would be useful if an illegal value was pa
Yo Hal!
On Sun, 05 Feb 2023 20:01:13 -0800
Hal Murray wrote:
> > Sadly some compilers will always complain if there is no default.
> > So I always add a default.
>
> We turn on -Wswitch-default
I like it.
> I'd like to turn on -Wswitch-enum
> That generates a handful of warnings that I'm w
Yo Hal!
On Sun, 05 Feb 2023 17:38:49 -0800
Hal Murray via devel wrote:
> 1439 default: {
> 1440 /* There should be a way for the compiler to
> check this. */ 1441 bool once =3D false;
> >>> CID 435753: Possible Control flow issues (DEADCODE)
> >>>
Yo All!
New Coverity issue in ntpsec. See below.
RGDS
GARY
---
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
g...@rellim.com Tel:+1 541 382 8588
Veritas liberabit vos. -- Quid es
Yo Hal!
On Fri, 20 Jan 2023 12:20:09 -0800
Hal Murray wrote:
> Your current code has 2 1/2 memory barriers. That's the same as my 2
> counter proposal.
I rather not take responsibility for the current code. Not mine.
And gpsd only has 2 threads, while ntpd has just one. The next
solution ne
Yo Hal!
On Thu, 19 Jan 2023 21:43:08 -0800
Hal Murray wrote:
> g...@rellim.com said:
> > Sadly, that no longer works on modern CPUs with out of order
> > execution. Unless wrapped in a mutex, or atomic, and that is now a
> > no-no.
>
> Do you have a good reference for that?
Many ariticle on
Yo Hal!
On Fri, 20 Jan 2023 02:11:29 -0800
Hal Murray wrote:
> The 31 bit idea seems strange/ugly to me. How did you decide to do
> it that way?
For back compatibility.
> Why is it better than 32 unsigned bits? Is there some case that
> works with 31 bits that breaks with 32?
Yeah, 2038.
>
Yo James!
How about you respond to my pending reviews dirst?
On Thu, 19 Jan 2023 13:27:54 -0800 (PST)
James Browning via devel wrote:
> If I were a maintainer of the NTPsec group, I could merge the
> following branches on my own. If only a developer, I could still
> approve other people's merg
Yo Greg!
On Sun, 15 Jan 2023 09:42:06 -0500
Greg Troxel wrote:
> > You can always build bad .o. But good practice is to build all .o
> > in a program or binary with the same setting. Otherwise a huge
> > number of ways to fail. That is why all gpsd c files start with:
> >
> > #include "../inc
Yo Greg!
On Sat, 14 Jan 2023 09:00:58 -0500
Greg Troxel wrote:
> "Gary E. Miller" writes:
>
> >> > 1: 64-bit time_t with 64-bit ints:
> >> > All known 64-bit distros (?)
> >> > Works after 2038
> >> > No change required.
> >>
> >> Do you mean "int64_t"?
> >
> > No, I m
Yo Greg!
On Sat, 14 Jan 2023 09:26:45 -0500
Greg Troxel wrote:
> >> Do the same thing that BSDs did: change time_t to in64_t and
> >> change the syscall codepoints. (Except you have to define
> >> something.)
> >
> > No, not change time_t. Add an incompatible alias to time_t.
>
> When y
Yo Greg!
On Sat, 14 Jan 2023 09:32:03 -0500
Greg Troxel wrote:
> "Gary E. Miller" writes:
>
> >> Which magically changes references to syscalls that use time_t, in
> >> the entire binary, to the new ones?
> >
> > Uh, once again, no. No "versioning". No syscalls are changed.
> >
> > Every e
Yo Hal!
On Sat, 14 Jan 2023 08:30:08 -0800
Hal Murray wrote:
> Does this problem go away (for another 68 years) if on 32 bit systems,
>we change the time_t in SHM to uint32_t?
No. Some ILP32 already moved to int64_t for time_t. Like all the BSDs.
> The SHM layout stays the same so all co
Yo Greg!
On Fri, 13 Jan 2023 19:46:15 -0500
Greg Troxel wrote:
> "Gary E. Miller" writes:
>
> >> Does Linux version syscalls? In NetBSD, we change the codepoints
> >> when the ABI changes, and there is kernel code to implement the old
> >> codepoint (but no header support) so old binaries sti
Yo Richard!
On Fri, 13 Jan 2023 19:08:10 -0600
Richard Laager via devel wrote:
> > So, looking only at option 4. The one that we can improve.
>
> I think you have captured the options correctly.
Plus the corrections from Greg.
> > That maintains compatibility with existing SHM users.
> > T
Yo Greg!
On Fri, 13 Jan 2023 20:20:48 -0500
Greg Troxel wrote:
> Greg Troxel writes:
>
> I just had a realization. What Linux is doing is more or less:
>
> Do the same thing that BSDs did: change time_t to in64_t and change
> the syscall codepoints. (Except you have to define something
Yo Greg!
On Fri, 13 Jan 2023 19:55:47 -0500
Greg Troxel wrote:
Sorry, you correctly point out I was sloppy and mistakes in
nomenclature.
See below for more.
> "Gary E. Miller" writes:
>
> > 1: 64-bit time_t with 64-bit ints:
> > All known 64-bit distros (?)
> > Works after 2038
>
Yo Greg!
On Fri, 13 Jan 2023 19:33:35 -0500
Greg Troxel wrote:
> [dropping ntpsec because they bounced my mail]
>
> "Gary E. Miller" writes:
>
> >> but int is ok in
> >> practice, on ILP32. On IP16L32, it's not, but we aren't building
> >> for PDP-11 any more :-)
> >
> > What is ILP32?
Yo All!
Looks like there are four cases to support with shmTime:
1: 64-bit time_t with 64-bit ints:
All known 64-bit distros (?)
Works after 2038
No change required.
2: 64-bit time_t with 32-bit ints:
All *BSD (?)
Works after 2038
No change required.
3: 32-bi
Yo Hal!
On Fri, 13 Jan 2023 13:50:23 -0800
Hal Murray wrote:
> I'm missing the big picture. I've been assuming that gpsd and ntpsec
> and everybody else will use time_t from the system header files.
> (without tweaking anything)
A valid assumption, until now. glibc on 32-bit, now tells us wwe
Yo James!
On Fri, 13 Jan 2023 13:43:38 -0800 (PST)
James Browning wrote:
> > On 01/13/2023 1:06 PM PST Hal Murray wrote:
> >
> >
> > If we make any changes to SHM, we should switch to a setup where
> > the memory is read only. The idea is to allow multiple readers.
> >
> > The trick to imple
Yo Hal!
On Thu, 12 Jan 2023 23:15:25 -0800
Hal Murray wrote:
> g...@rellim.com said:
> > Recent glibc (2.34 and up) and recent Linux kernels, allow 64 bit
> > time_t on 32-bit Linux without much work.
>
> What does "without much work" mean?
See commit 19d76e95312b03028752d57e76098d56adac63d
Yo Hal!
On Fri, 13 Jan 2023 13:06:28 -0800
Hal Murray wrote:
> If we make any changes to SHM, we should switch to a setup where the
> memory is read only. The idea is to allow multiple readers.
And how do we do that? Without mutexes or atomics? The "new normal"
is to avoid those because they
Yo Greg!
On Fri, 13 Jan 2023 07:11:49 -0500
Greg Troxel wrote:
> "Gary E. Miller" writes:
>
> > Recent glibc (2.34 and up) and recent Linux kernels, allow 64 bit
> > time_t on 32-bit Linux without much work.
>
> Interesting to hear; I had assumed time_t on Linux was changed long
> ago to in
Yo All!
Greg is not on devel@ntpsec, and asked me to cross post this for him.
See below.
RGDS
GARY
---
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
g...@rellim.com Tel:+1 541 382 8588
Yo James!
On Fri, 13 Jan 2023 08:49:34 -0800 (PST)
James Browning wrote:
> > This makes my head hurt...
>
> IIRC there are a few users of those interfaces; linuxptp, gpsd,
> classic NTP, NTPsec, and chrony.
Multiplied by the number of distros that carry each, and update on their
own schedul
Yo Richard!
On Fri, 13 Jan 2023 13:43:06 -0600
Richard Laager wrote:
> On 1/12/23 19:10, Gary E. Miller via devel wrote:
> > How does ntpd know what size time_t to use? And thus know the size
> > of shmTime? How do we know portably, preserving backwards and
> > f
Yo All!
Cross-posted to gpsd-dev and devel@ntpsec.org
Recent glibc (2.34 and up) and recent Linux kernels, allow 64 bit
time_t on 32-bit Linux without much work.
But...
How to get that 2038 compatible time to ntpd and chronyd? That is a
much bigger problem.
Extracted from include/ntpshm.h:
s
Yo folkert!
On Tue, 3 Jan 2023 08:58:40 +0100
folkert wrote:
> Can I please send the patch via e-mail? I've been struggeling with
> gitlab for an hour and whatever I do it keeps complaining that I'm not
> allowed to push to the project (my own clone, in a branch).
I think you already sent the p
Yo folkert!
> 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.
>
> On Mon, 2 Jan 2023 15:10:06 +0100
> folkert via devel wrote:
>
> > Just noticed https://n
Yo folkert!
Lost me. What about sntp do you want to put on gitlab?
On Mon, 2 Jan 2023 15:10:06 +0100
folkert via devel wrote:
> 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 followi
Yo Fred!
On Thu, 22 Dec 2022 17:00:37 -0800 (PST)
Fred Wright via devel wrote:
> On Wed, 21 Dec 2022, Hal Murray via devel wrote:
>
> > Google says:
> > https://developers.google.com/time/smear
> > We encourage anyone smearing leap seconds to use a 24-hour linear
> > smear from noon to noon U
Yo Fred!
On Wed, 21 Dec 2022 18:21:39 -0800 (PST)
Fred Wright via devel wrote:
> On Wed, 21 Dec 2022, Hal Murray via devel wrote:
>
> > Does anybody use it?
> > Do any distros build with it enabled?
> > Should we add an "#warn untested" to the code?
>
> If some systems need leap-smeared time
r; Mon, 21 Nov 2022 23:09:39 +0000 (UTC)
> >>>> Received: from spidey.rellim.com (rellim.com
> >>>> [IPv6:2001:470:e815::19]) by rellim.com (Postfix) with ESMTPSA id
> >>>> 9D42120001F for; Mon, 21 Nov 2022 15:09:39
> >>>> -0800 (PST) Da
> <mailto:devel-requ...@ntpsec.org?subject=unsubscribe>
> List-Archive:<https://lists.ntpsec.org/pipermail/devel/>
> List-Post:<mailto:devel@ntpsec.org>
> List-Help:<mailto:devel-requ...@ntpsec.org?subject=help>
> List-Subscribe:<https://lists.ntpsec.org/
gt; >> Message-ID:<20221121150932.5ed30...@spidey.rellim.com>
> >> Organization: Rellim
> >> X-Mailer: Claws Mail 4.1.1 (GTK 3.24.34; x86_64-pc-linux-gnu)
> >> MIME-Version: 1.0
> >> X-BeenThere:devel@ntpsec.org
> >> X-Mailman-Version: 2.1.39
Yo All!
Testing 7-8-9
RGDS
GARY
---
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
g...@rellim.com Tel:+1 541 382 8588
Veritas liberabit vos. -- Quid est veritas?
"If you can'
Yo All!
Test 4-5-6
RGDS
GARY
---
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
g...@rellim.com Tel:+1 541 382 8588
Veritas liberabit vos. -- Quid est veritas?
"If you can't m
Mailman-Version: 2.1.38
> Precedence: list
> List-Id: Developer discussion
> List-Unsubscribe:<https://lists.ntpsec.org/mailman/options/devel>,
> <mailto:devel-requ...@ntpsec.org?subject=unsubscribe>
> List-Archive:<https://lists.ntpsec.org/pipermail/devel/>
&
Yo All!
Testing 1-2-3...
RGDS
GARY
---
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
g...@rellim.com Tel:+1 541 382 8588
Veritas liberabit vos. -- Quid est veritas?
"If you c
Yo Hal!
On Thu, 16 Jun 2022 19:33:07 -0700
Hal Murray via devel wrote:
> Has anybody seen the serial port get stuck?
Not me, but I have heard reports. Usually a voltage mismatch.
> It's software/kernel. I can see the bits with a scope.
You can't just cat/minicom the serial port?
And stty s
Yo All!
mes showed me how to duplicate this bug. Obviously a clang 13 optimier
bug. Fix pushed to git head. Please test.
Users should prolly avoid clang 13 until the bug is fixed in clang.
RGDS
GARY
---
Gary E. Miller Rel
Yo jamesb...@jamesb192.com!
On Sat, 14 May 2022 22:27:13 -0400 (EDT)
"jamesb...@jamesb192.com jamesb192--- via devel"
wrote:
> > On 05/14/2022 8:53 PM Gary E. Miller via devel
> > wrote:
> >
> >
> > Yo Hal!
> >
> > On Sat, 14 May
Yo Hal!
On Sat, 14 May 2022 17:42:59 -0700
Hal Murray via devel wrote:
> I'm cc-ing devel so this doesn't get lost on gitlab. Let's move the
> discussion real email..
Not yet in the delvel emailarchives: What distro is broken by this?
RGDS
GARY
---
Yo Hal!
On Sat, 14 May 2022 17:42:59 -0700
Hal Murray via devel wrote:
> I'm cc-ing devel so this doesn't get lost on gitlab. Let's move the
> discussion real email..
>
>
> > include/ntp_fp.h:58 defines l_fp as a uint64_4, I can find no
> > current contrary definitions.
>
> We need to mak
Yo Hal!
On Wed, 11 May 2022 01:53:30 -0700
Hal Murray wrote:
> > I like you suggestion of ntpd using "-g" to get the system time
> > close, before checking any certificates.
>
> It was Richard's suggestion, not mine. The idea was to only skip the
> date checks and do the rest of the certifi
Yo Hal!
On Tue, 10 May 2022 10:26:08 -0700
Hal Murray wrote:
> Gary said:
> >> Should we do something like set the time to the time stamp of the
> >> drift file? (if it is significantly newer than the current time)
>
> > Nope. Don't get in a fight with the OS.
>
> Could you please say mo
Yo Hal!
On Mon, 09 May 2022 00:38:34 -0700
Hal Murray via devel wrote:
> Does anybody know how the initial time gets set on a Raspberry Pi --
> before ntpd gets called?
It depends. Some use swclock, some use ntpclient, some use an RTC,
some use a GNSS time.
> I have a recently setup system th
Yo All!
From [time-nuts]: predictions of a negative leap second in 2027!
See below, and attached.
RGDS
GARY
---
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
g...@rellim.com Tel:+1 541 382 85
Yo All!
openssl 3.0.0 is becoming an issue. See:
https://gitlab.com/NTPsec/ntpsec/-/issues/734
We have been stolling towards a release, what do we need to get one
out with openssl 3.0?
RGDS
GARY
---
Gary E. Miller Rellim 1
Yo Hal!
On Wed, 16 Mar 2022 18:44:29 -0700
Hal Murray wrote:
> > You should be able to login here:
> > https://scan.coverity.com/dashboard
>
> I get to a page where it wants me to Authorize Coverity Scan.
>
> What's that all about?
You are authorizing them to scna NTPsec directly from the G
Yo Hal!
On Wed, 16 Mar 2022 16:01:17 -0700
Hal Murray wrote:
> I don't know my way around coverty.
You should be able to login here:
https://scan.coverity.com/dashboard
> Does this have a meaning?
> > ** CID 349664: Uninitialized variables (UNINIT)
349664 is the serial number of the defe
Yo All!
Another coverity found defect. See below.
RGDS
GARY
---
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
g...@rellim.com Tel:+1 541 382 8588
Veritas liberabit vos. -- Quid e
Yo All!
New coverity found defect in NTPsec.
See below.
RGDS
GARY
---
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
g...@rellim.com Tel:+1 541 382 8588
Veritas liberabit vos. --
Yo Hal!
On Tue, 22 Feb 2022 14:39:21 -0800
Hal Murray via devel wrote:
> They don't work. See https://gitlab.com/NTPsec/ntpsec/-/issues/729
>
> There is a single line of code that disables them.
>
> They are less secure. But is that "less" practical or theoretical?
>
> They are deprecated i
Yo Udo!
On Sat, 12 Feb 2022 12:35:43 +0100
Udo van den Heuvel wrote:
> On 12-02-2022 07:36, Gary E. Miller via devel wrote:
> > A capture of the raw NMEA would be helpful.
>
> The other gps18x does not show the wrong date.
> So would a reset of the 'wrong date'
Yo Udo!
A capture of the raw NMEA would be helpful.
On Sat, 12 Feb 2022 06:52:47 +0100
Udo van den Heuvel via devel wrote:
> On 12-02-2022 06:45, Hal Murray wrote:
> >
> > devel@ntpsec.org said:
> >> Is this an effect? I get loads of these:
> >> Feb 6 00:00:28 srfplnk2 ntpd[510014]: REFCLOC
Yo Hal!
On Tue, 08 Feb 2022 02:55:10 -0800
Hal Murray wrote:
> Have you got it working yet?
I'm not sure which you are talking about. The broken RES360, or the RES720?
I have a firmware update that is supposed to fix my RES 360, but I'm
woorkong on the very different RES 720 right now. I'll
Yo All!
Another twist on GPS Week Roll Over mess.
Yesterday I fire up my Trimble RES360. And it is 2019 all over again.
I peeked at the TSIP binary, and it is sending a negative GPS Time OF
Week (TOW), and an extended GPS week of 2048. For reference this week
is GPS week 2195. Transmitted as w
Yo Hal!
On Fri, 28 Jan 2022 15:59:03 -0800
Hal Murray via devel wrote:
> I think I've figured out part of what is going on. There is code
> that I think is trying to do the right thing with dates past 32 bits
> on systems with a 32 bit time_t.
>
> I'm assuming that is not an interesting case.
Yo Hal!
On Fri, 28 Jan 2022 22:19:15 -0800
Hal Murray wrote:
> > I handle the regressions in gpsd so no need to fix them up. They
> > have always had a line:
>
> Good. But that doesn't get the refclock drivers in ntpd. I've been
> discussing refclock_nmea.
>
> > So that is two roll overs,
Yo Hal!
On Wed, 26 Jan 2022 19:05:17 -0800
Hal Murray wrote:
> Thanks.
>
> Gary said:
> >> We need 2 pivot dates, one for the 2 digit year fixup, another for
> >> the WNRO fixup.
>
> > More than 2, as WKRO happens every 1024 weeks.
>
> I don't understand how you are counting. I see one p
Yo Hal!
Sorry for the dealy, my inbox got full.
On Mon, 17 Jan 2022 22:41:36 -0800
Hal Murray via devel wrote:
> I think I've figured out what was going on. There are 2 stages of
> fixup. One is for the 2 digit year. The other is for the WNRO. The
> trick is that the year fixup has to let
Yo Hal!
On Wed, 29 Dec 2021 13:31:44 -0800
Hal Murray via devel wrote:
> Gary said:
> >> The code I was expecting doesn't know anything about leaps.
> >> It would be close to:
> >> while (t < PIVOT) t += 1024*7*86400
>
> > Which will break after 1024 weeks. Which sounds like a lot, but
> >
Yo Hal!
On Wed, 29 Dec 2021 03:02:00 -0800
Hal Murray via devel wrote:
> Gary said:
> > Basically, if the GPS reports more the 17 leap seconds, then the
> > time has to be aster 1 Jan 2017.
>
> Thanks.
>
> I assume the leap second tangle is so avoid breaking some very old
> test cases by bum
1 - 100 of 1002 matches
Mail list logo
