> On 12/23/2022 7:51 AM PST NTPfiend via users wrote:
>
>
> My instance of ntpsec gave up after just over a year uptime, so I went for a
> re-installation (later R Pi, now 64 bit). Today (23 Dec) I attempted to run
> clockmaker but it did not get far:
>
> [Line 210
I misunderstood something.
Now I think I get it. I closed one of my existing MRs; the one that added the
PI 3 Model B+ hardware to clockmaker. That was the one that would have
conflicted with the PEP8 cleanup of clockmaker.
I created a new MR that adds the 3B+ HW to clockmaker in a PEP8-complia
On Thursday, September 6, 2018 10:56 PM, "Mark Atwood, Project Manager"
wrote:
> Thank you Mike! Please submit the PEP8 MR after you've fixed the merge
> conflict. I will review your existing MRs.
Ok, will do.
___
devel mailing list
On Thursday, September 6, 2018 10:14 PM, Paul Theodoropoulos via devel
wrote:
> You might want to take a skim through those recent-ish commit to the
> howto, as I'm sure there's been further divergence from clockmaker that
> I introduced over the last month or two.
Thanks for
on numbering and the other adds the Pi Model 3B+ to clockmaker.
>
> I have 2 other branches that I haven't submitted MR for yet. One is PEP8
> clean up on clockmaker. There will be at least one merge conflict here,
> assuming the Model 3B+ h/w MR is accepted first. I was waiting to
On 9/6/2018 18:49 PM, MIKE MAJOR via devel wrote:
I have another branch in the queue. It creates directories and
permissions on /var/lib/ntp & /var/log/ntpstats in clockmaker. These
directories are not created by clockmaker. Evidence of the missing
directories were the errors showin
Hi everyone,
I'd like to tell you what I've been working on. I submitted MRs for the HOWTO
section numbering and the other adds the Pi Model 3B+ to clockmaker.
I have 2 other branches that I haven't submitted MR for yet. One is PEP8 clean
up on clockmaker. There will be at least one merge
Yo Eric!
On Sat, 10 Mar 2018 23:41:52 -0500
"Eric S. Raymond" <e...@thyrsus.com> wrote:
> Gary E. Miller via devel <devel@ntpsec.org>:
> > To follow up on this, the user had ./clockmaker --config fail to
> > install scons. Probably failed earlier. No war
Gary E. Miller via devel <devel@ntpsec.org>:
> To follow up on this, the user had ./clockmaker --config fail to install
> scons. Probably failed earlier. No warning messages. The user then
> ran clockmaker --build, which silently failed, because of no
> scons.
That's weir
Gary E. Miller via devel <devel@ntpsec.org>:
> Yo Eric!
>
> A user found a bug in the clockmaker howto:
>
> Run "sudo clockmaker --config". This will do most of the tricky
> OS and hardware configuration; also system software updates and
> prer
Yo All!
On Sat, 10 Mar 2018 16:07:51 -0800
"Gary E. Miller via devel" <devel@ntpsec.org> wrote:
> clockmaker is giving a user warnings like:
> This function should not be run as root.
>
> But he has no idea which command in clockmaker.
>
> Can we g
Yo All!
clockmaker is giving a user warnings like:
This function should not be run as root.
But he has no idea which command in clockmaker.
Can we get a verbose option?
Anyone have an idea what changed in Raspbian to start throwing this warning?
RGDS
GARY
Yo Eric!
A user found a bug in the clockmaker howto:
Run "sudo clockmaker --config". This will do most of the tricky
OS and hardware configuration; also system software updates and
prerequisites for the timeserver software
unless the user put clockmaer in usr/bin, it
13 matches
Mail list logo
