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
From: Hal Murray
To:devel@ntpsec.org
Subject: Testing
Does anybody test our code on Apple? Solaris?
In order to test 32 bit and 64 bit big and little endian hosts with the
Trimble driver, I have been using:
LE32: Raspberry Pi 3B with Raspbian
LE64: Xeon with Gentoo
BE32: Power Mac G4 with Fre
On Thu, May 02, 2024 at 02:17:18AM -0700, Hal Murray via devel wrote:
> Does anybody test our code on Apple? Solaris?
I do some of my initial dev work on macOS, but I don't run ntpd on macOS. My
production environment for NTPsec is Linux. I worked with Solaris x86 a few
years ago since I was i
On Wed, Sep 20, 2023 at 08:02:51PM -0700, Hal Murray via devel wrote:
>
> Does anybody have a recipe (or pointer to one) for how to get a system
> running
> without any IPv6?
net.ipv6.conf.all.disable_ipv6=1
> I want something such that isc_net_probeipv6_bool() will return false.
>
> Do we hav
Yo Paul!
On Mon, 21 Nov 2022 19:27:12 -0800
Paul Theodoropoulos wrote:
> Yeah, I would be curious what the full infrastructure is with paths,
> but as you mentioned, Thanksgiving lingers near.
No one still with NTPsec likes it, but inertia is strong.
> I've used DJB's dnscache for, well I gues
Yeah, I would be curious what the full infrastructure is with paths, but
as you mentioned, Thanksgiving lingers near.
I've used DJB's dnscache for, well I guess it would be decades now, for
near-line lookup caching, it is really a wonderful thing, but it
"requires" many patches, and has no IPv
Yo Paul!
Email gets into mailman, and archives, quickly. Then mailman, on
lists.ntpsec.org, was talking directly mx.ntpsec.org, sending one email
every 75 seconds.
Now I have mailman sending email to the postfix on lists.ntpsec.org, and
that sends many emails in parallele to mx.ntpsec.org, that
Yo Paul!
On Mon, 21 Nov 2022 16:14:33 -0800
Paul Theodoropoulos wrote:
> Seven seconds round-trip. I'd say the issues are formally mitigated.
Maybe because DNS is recently cached? Something else to look at.
>
> On 11/21/2022 16:13 PM, Paul Theodoropoulos via devel wrote:
> > And this reply t
Seven seconds round-trip. I'd say the issues are formally mitigated.
On 11/21/2022 16:13 PM, Paul Theodoropoulos via devel wrote:
And this reply took about one minute thirty seconds round-trip.
Screws up the line, but in a good way.
On 11/21/2022 16:10 PM, Paul Theodoropoulos via devel wrote:
And this reply took about one minute thirty seconds round-trip.
Screws up the line, but in a good way.
On 11/21/2022 16:10 PM, Paul Theodoropoulos via devel wrote:
Inserted into stream:
Mon, 21 Nov 2022 15:09:32 -0800
Received here:
Mon, 21 Nov 2022 15:46:32 -0800
So, about 3 hours, down to a
Inserted into stream:
Mon, 21 Nov 2022 15:09:32 -0800
Received here:
Mon, 21 Nov 2022 15:46:32 -0800
So, about 3 hours, down to about 90 minutes, down to about 37 minutes.
Pretty smooth line.
Return-path:
Envelope-to:p...@anastrophe.com
Delivery-date: Mon, 21 Nov 2022 15:46:32 -0800
Received
Better. Dropped 18:54:41, delivered 20:22:26, so an hour thirty minutes roughly.
Return-path:
Envelope-to:p...@anastrophe.com
Delivery-date: Sun, 20 Nov 2022 20:22:26 -0800
Received: from mx.ntpsec.org ([140.211.9.57]:45636)
by relay.anastrophe.com with esmtps (TLS1.3) tls
TLS_ECDHE_RSA
Worked for me. Thanks.
What did you do/find? Is it likely to stay working?
--
These are my opinions. I hate spam.
___
devel mailing list
devel@ntpsec.org
https://lists.ntpsec.org/mailman/listinfo/devel
Yo Paul!
There were 500k messages backed up on the mailman queue. I just deleted
them all. With the queue empty, mailman is sending one email every 75
seconds. No idea why, still looking at it.
On Sun, 20 Nov 2022 16:03:17 -0800
Paul Theodoropoulos wrote:
> Apparently submitted at:
>
> Sund
Apparently submitted at:
Sunday, 20 Nov 2022 12:00:06 -0800
Received here (also on US West coast):
Sunday, 20 Nov 2022 15:09:33 -0800
Three hours is certainly dramatically better than the three months we were
seeing.
Full header if it helps analysis:
Return-path:
Envelope-to:p...@anastroph
On Thu, Jul 23, 2020, at 10:59 AM Gary E. Miller via devel
wrote:
>
> Yo All!
>
> Testing 1-2-3. This list has been down since 13 Jul...
Funny, It looks like there were a couple of posts two days ago, and
before that nobody posting for a week. I think it was just sleeping or
hunting rabbits.
___
I "test" buildprep for Debian for every release, because I spin up a
small minimal Debian instance for each release.
One of my todo's is to collate and add to the docs the set of packages
I have apt-get each time.
On Fri, Sep 29, 2017 at 11:18 PM Hal Murray via devel wrote:
>
>
> Should we test
Sorry for the delay. I got distracted on other things.
While I think of it, did TESTFRAME dump floating point numbers in ASCII or
hex? If ASCII, there are likely to be round off errors when you read them
back in. Were there any floating point numbers that were read back in? (as
compared t
Hal Murray via devel writes:
> Are the specs and implementation for IEEE floating point tight enough so that
> I should get the exact same result if I run a test on a different CPU
> chip?
Formally yes, if you aren't straying into denormals and you keep
yourself to elementary operations that actu
Yo Hal!
On Mon, 15 Jul 2019 17:15:34 -0700
Hal Murray via devel wrote:
> Are the specs and implementation for IEEE floating point tight enough
> so that I should get the exact same result if I run a test on a
> different CPU chip?
Better than it used to be, but you will still want to use a guar
On Mon, Jul 15, 2019, 5:15 PM Hal Murray via devel wrote:
>
> tenterl...@gmail.com said:
> > I come from a scientific background, where we compare results somewhat as
> > analog values. If the test result is off the expected by 1000%, that's
> bad.
> > If it's off 1%, better. If the error is .000
tenterl...@gmail.com said:
> I come from a scientific background, where we compare results somewhat as
> analog values. If the test result is off the expected by 1000%, that's bad.
> If it's off 1%, better. If the error is .1%, probably within achievable
> accuracy.
There is a difference b
Please excuse an outsider jumping into the conversation.
AIUI, the testing under discussion is what I think of as the system
programming type - if we have inputs A and B to a black box, and the
test reproduces output C exactly, bit-for-bit, then the test is a
success, otherwise it is a complete fa
Hal Murray :
>
> > It's...hm...maybe a good way to put it is that the structure of the NTPsec
> > state space and sync algorithms is extremely hostile to testing.
>
> I still don't have a good understanding of why TESTFRAME didn't work. I
> can't
> explain it to somebody.
>
> We've got
> co
> Can you get them to specify exactly what they want?
One thing to add to the list if you are going to collect NTP data...
If you know that the clocks at both ends are accurate, rawstats will give you
the transit times in each direction.
NTP assumes the transit times in each direction are equal
Mark Atwood, Project Manager :
> Oh, believe me, cloud scale devops shops know what to do with all the
> timing information.
Can you get them to specify exactly what they want?
--
http://www.catb.org/~esr/";>Eric S. Raymond
___
devel m
> This would actually be pretty easy to do, mechanically speaking. The
hard question is what you do with this timing information once you have it.
Oh, believe me, cloud scale devops shops know what to do with all the
timing information.
On Sun, Jul 14, 2019 at 3:19 PM Eric S. Raymond wrote:
>
> It's...hm...maybe a good way to put it is that the structure of the NTPsec
> state space and sync algorithms is extremely hostile to testing.
I still don't have a good understanding of why TESTFRAME didn't work. I can't
explain it to somebody.
We've got
code mutations
hidden variables i
Mark Atwood :
> I want to encourage Hal to think of ways of cracking these problems.
>
> Especially the idea of verifying key parts of the state space, even if
> we can't verify it all.
I wish him the best of luck...
> And especially if there was a way to usefully log the relative timing
> of va
> Especially the idea of verifying key parts of the state space, even if we
> can't verify it all. And especially if there was a way to usefully log the
> relative timing of various important state transitions. (That is something
> on the wishlist of the AWS NTP Kronos team.)
What are they loo
Hal Murray :
> Your writeup focuses on code mutations rather than state space. (Or maybe I
> didn't read what you intended.)
Perhaps I could have been clearer. But those two problems run
together in my mind becauase of what unifies them and contrasts
with the GPSD and reposurgeon cases.
It's..
e...@thyrsus.com said:
> A lot of configuration options - even things like minsane - effectively
> change the FSM.
Right. But as you said, that's a configuration option.
> Sure, you can think of the config as part of the input state - this isn't a
> code mutation. But it also means you can on
Hal Murray :
> I agree that the core FSM is complicated, but how often do we change it?
A lot of configuration options - even things like minsane - effectively change
the FSM.
Sure, you can think of the config as part of the input state - this
isn't a code mutation. But it also means you can only
e...@thyrsus.com said:
> https://blog.ntpsec.org/2017/02/22/testframe-the-epic-failure.html
> Read that and think about it for a while. This is a very hard problem. I
> hit it and bounced.
Thanks.
>From the blog page:
> In effect, the entire logic of the sync algorithms is a gigantic free
> p
Hal Murray via devel :
> Eric: What is the name/term for your attempt at capturing and replaying
> things? Is there a good writeup of why it didn't work?
https://blog.ntpsec.org/2017/02/22/testframe-the-epic-failure.html
Read that and think about it for a while. This is a very hard
problem. I
Yo Hal!
On Thu, 21 Mar 2019 21:49:31 -0700
Hal Murray via devel wrote:
> > What's your environment? I'm passing "ntp" to getaddrinfo.
> > Ah, that's the bug. Don't do that. There is no offical tcp/ntp
> > port assigned. So trying to look it up is not going to work
> > well...
>
> For "n
> What's your environment? I'm passing "ntp" to getaddrinfo.
> Ah, that's the bug. Don't do that. There is no offical tcp/ntp port
> assigned. So trying to look it up is not going to work well...
For "not going to work", it took a long time to fail.
Fix pushed.
--
These are my opinions.
Gary,
It works with a mix of NTS and NTP, I removed the NTP to force it to sync
with your servers.
All seems OK now.
On Fri, Mar 22, 2019, 12:20 PM Gary E. Miller wrote:
> Yo Sanjeev!
>
> On Fri, 22 Mar 2019 08:31:34 +0800
> Sanjeev Gupta wrote:
>
> > I removed all non-NTS servers from my co
Yo Sanjeev!
On Fri, 22 Mar 2019 08:31:34 +0800
Sanjeev Gupta wrote:
> I removed all non-NTS servers from my config,and I am now synced!!!
Weird. I can run with a mix of plain NTPD and NTS/NTPD.
> No rest for the helpful: How do I check if I am an NTS server?
I like Hal's suggestions. I also
Yo Hal!
On Thu, 21 Mar 2019 17:49:55 -0700
Hal Murray via devel wrote:
> > 2019-03-22T03:56:32 ntpd[21039]: NTSc: nts_probe: DNS error trying
> > to contact pi3.rellim.com: -8, Servname not supported for
> > ai_socktype
>
> What's your environment? I'm passing "ntp" to getaddrinfo.
Ah, tha
> No rest for the helpful: How do I check if I am an NTS server?
The real check is that somebody can connect to your server.
Other maybe helpful sources of info:
netstat -tl
Should show:
tcp0 0 0.0.0.0:ntp 0.0.0.0:* LISTEN
tcp6 0 0 [::]:ntp
> Been runnig for a few hours now. ntpq -pn output:
...
> And the log is here: https://pastebin.com/fM9uDwVi
Thanks.
> 2019-03-22T03:56:32 ntpd[21039]: NTSc: nts_probe: DNS error trying to contact
> pi3.rellim.com: -8, Servname not supported for ai_socktype
What's your environment? I'm passi
Gary,
I removed all non-NTS servers from my config,and I am now synced!!!
root@ntpmon:~/ntpsec# ntpq -p
remote refid st t when poll
reach delay offset jitter
==
Gary,
Adding this to /etc/services seems to fix the issue:
ntp 123/tcp # Network Time Protocol
I now see:
-pi3.rellim.com .PPS.1 84 64
37 197.8958 0.5317 0.4966
-kong.rellim.com 204.17.205.1
Yo Sanjeev!
> > Looks good. What is your server so I can try to connect back?
> My server is ntpmon.dcs1.biz . It is in the pool, BTW.
I can't connect to any NTS from kong now. Not getting any cookies.
Some of my other 3 still work in various combinations.
I'm not putting NTS on my one pool s
On Fri, Mar 22, 2019 at 7:24 AM Gary E. Miller via devel
wrote:
> > I have been lurking and trying to set up NTS to talk to the rellim.com
> > servers. This is a recent git head.
>
> Cool.
>
I just did a git pull and rebuilt.
> > My ntp.conf snippet:
> >
> > nts enable
> > nts cert /etc/letse
Yo Sanjeev!
On Fri, 22 Mar 2019 07:14:29 +0800
Sanjeev Gupta via devel wrote:
> I have been lurking and trying to set up NTS to talk to the rellim.com
> servers. This is a recent git head.
Cool.
> My ntp.conf snippet:
>
> nts enable
> nts cert /etc/letsencrypt/live/ntpmon.dcs1.biz/fullchain.
On Sun, Nov 04, 2018 at 09:47:14PM -0800, Hal Murray via devel wrote:
> [Was: Subject: Re: ntpleapfetch broken on FreeBSD 11.2 or NetBSD 8.0]
>
> > I was working on that a little try checking out merge request !831
>
> How do I do that?
>
> That should be simple, but it's not in my working set.
On Sun, Nov 4, 2018 at 9:47 PM Hal Murray via devel
wrote:
> [Was: Subject: Re: ntpleapfetch broken on FreeBSD 11.2 or NetBSD 8.0]
>
> > I was working on that a little try checking out merge request !831
>
> How do I do that?
>
> That should be simple, but it's not in my working set. I think I a
Replying to both Ian and the list - sent about 2018-09-14T1835Z.
On 09/14/2018 02:21 PM, Ian Bruene via devel wrote:
>
> (test)
>
> --
> /"In the end; what separates a Man, from a Slave? Money? Power? No. A
> Man Chooses, a Slave Obeys."/ -- Andrew Ryan
>
> /"Utopia cannot precede the Utopian.
Eric said:
> I've never tried do describe that kind of testing because it's not easy to
> tell people without prior experience running the clients what a success/
> failure indication looks like. Of course alarm bells would go off on a
> crash, but the most definite thing I could say otherwise is
Hal Murray :
>
> e...@thyrsus.com said:
> > Alas, the client tools are difficult ebnough to test-jig that I have to
> > hand-test under Python 3 before releases. I have a routine for this and I
> > assume Ian does as well.
>
> How much testing do you do by hand? Is that written down anyplace?
e...@thyrsus.com said:
> Alas, the client tools are difficult ebnough to test-jig that I have to
> hand-test under Python 3 before releases. I have a routine for this and I
> assume Ian does as well.
How much testing do you do by hand? Is that written down anyplace? Should
it be on the relea
Hal Murray via devel :
> >From packaging/packaging.txt
>
> > The shebang lines in our Python scripts point to
> > "python". Part of our standard tests check that
> > you can change that to "python3" without breaking
> > anything.
>
> What sort of testing is that? How do I run it on my setup?
A
On Tue, Mar 20, 2018 at 09:03:45PM -0700, Hal Murray via devel wrote:
> What sort of testing is that? How do I run it on my setup?
Our Gitlab CI runs the builds and all of our python tests using python3 (using
the latest python3 from docker) on every build. See
https://gitlab.com/NTPsec/ntpse
Yo Hal!
On Tue, 20 Mar 2018 21:03:45 -0700
Hal Murray via devel wrote:
> From packaging/packaging.txt
>
> > The shebang lines in our Python scripts point to
> > "python". Part of our standard tests check that
> > you can change that to "python3" without breaking
> > anything.
>
> What sort
Hal Murray via devel :
> Would it help if we made a chart of the status of various features cross
> OSes/distros? How many different OSes/distros do we support? Can it fit on
> a page? ...
>
> How many different levels of testing are there? I'm thinking of something
> like 0-3, where 0 is u
hmur...@megapathdsl.net said:
> You can get some interesting data if you kick up the memory for the MRU
> list.
> A US/NA server needs 325K to hold everything for a bit over a day.
Argh. I forgot a key piece of info.
That's on a box signed up for 100 megabits of IPv4 and IPv6.
--
These are
On Wed, Dec 20, 2017 at 02:50:55PM -0800, Gary E. Miller via devel wrote:
> Yo Matthew!
>
> On Tue, 19 Dec 2017 23:05:37 -0500
> Matthew Selsky via devel wrote:
>
> > > If dev with merge-approver power pushes to a branch and then merges
> > > it, how is the entailed risk any different from a dir
Yo Matthew!
On Tue, 19 Dec 2017 23:05:37 -0500
Matthew Selsky via devel wrote:
> > If dev with merge-approver power pushes to a branch and then merges
> > it, how is the entailed risk any different from a direct push?
>
> We can have gitlab enforce that all CI builds must pass before
> merge.
On Wed, Dec 06, 2017 at 02:49:07PM -0500, Eric S. Raymond wrote:
> Matthew Selsky via devel :
> > On Wed, Dec 06, 2017 at 12:25:14PM -0500, Eric S. Raymond via devel wrote:
> >
> > > I have a different plan. I always write doc patches as part of my
> > > change commits; my discipline is to preven
Hal Murray :
> Even with something like a simple bug fix, some are easy to test and very
> unlikely to break anything else and some can't be tested by the fixer and
> some have potential to break something else.
That is so. I could live with a sytem that made some sensible distinctions
along th
Jason Azze via devel :
> Everyone pushes commits to a single working branch.
> These commits are built and tested by the CI automation.
> IFF the code builds and tests pass then the CI system auto-merges with
> the master branch.
> If an auto-merge isn't possible, it gets bounced to a human for int
>> How important is your individual way of doing things? Would you
>> be willing to tolerate some inconvenience if that made the rest of us
>> more productive?
> In principle, yes. I'd need to be persuaded that the net was positive -
> that the rest of you got sped up more than I got slowed down
On Wed, Dec 6, 2017 at 2:22 PM, Matthew Selsky via devel
wrote:
> We also don't have formal code reviews (before commit) since many devs push
> directly to "master". So we can't enforce any policies to code before they
> get committed to master.
>
> At some point, maybe soonish, can we stop pu
On 12/07/2017 07:43 AM, Eric S. Raymond via devel wrote:
How important is your individual way of doing things? Would you be willing
to tolerate some inconvenience if that made the rest of us more productive?
In principle, yes. I'd need to be persuaded that the net was positive -
that the res
Hal Murray :
>
> >> How many of your changes need to actually hit the repo in less than 24
> hours?
> > Depends on whether you think rapidly clearing bugs is important. I do.
>
> Why is that important? My 24 hours was a guess at the long tail. Who is
> going to notice if you fix a bug but it
>> How many of your changes need to actually hit the repo in less than 24
hours?
> Depends on whether you think rapidly clearing bugs is important. I do.
Why is that important? My 24 hours was a guess at the long tail. Who is
going to notice if you fix a bug but it doesn't appear in HEAD unt
Hal Murray :
> Are you carefully monitoring things? Do you look at the graphs every day?
Not every day. I do often have ntpmons watching one pr more of them.
> What configurations are you testing? Pool? PPS? Is your network connection
> flakey? (WiFi can be a good test case.)
Yes to the f
>> Your version of "pretty stable" doesn't match mine.
> Probably not. To a first approximation I judge "pretty stable" by the
> burn-in time on my Pis. If it runs for long periods of time on all six with
> no anomalies, it's stable.
I don't consider that to be much testing, but you didn't actua
On 12/06/2017 04:03 PM, Hal Murray via devel wrote:
Many years ago, a friend showed me an article in a bicycle magazine about how
to get ready for a race or big ride. It had all the expected things about
getting your bike ready. It also included ironing your shirt. ??? The idea
was that if
devel@ntpsec.org said:
> I have a different plan. I always write doc patches as part of my change
> commits; my discipline is to prevent code and docs from getting out of sync
> in the first place.
I agree that documentation should be kept up to date.
> I'm not opposed to giving the docs an occa
Hal Murray :
>
> > If dev with merge-approver power pushes to a branch and then merges it, how
> > is the entailed risk any different from a direct push?
>
> We could add a policy that somebody else do the push, presumably after
> checking the code. With details of "check" TBD.
>
> How many o
> If dev with merge-approver power pushes to a branch and then merges it, how
> is the entailed risk any different from a direct push?
We could add a policy that somebody else do the push, presumably after
checking the code. With details of "check" TBD.
How many of your changes need to actual
Matthew Selsky via devel :
> On Wed, Dec 06, 2017 at 12:25:14PM -0500, Eric S. Raymond via devel wrote:
>
> > I have a different plan. I always write doc patches as part of my
> > change commits; my discipline is to prevent code and docs from getting out
> > of sync in the first place.
>
> Does
Hal Murray :
>
> e...@thyrsus.com said:
> > Well, normally it would be a longer freeze, but we're doing this to roll out
> > a bug fix on code that has been pretty stable.
>
> Your version of "pretty stable" doesn't match mine.
Probably not. To a first approximation I judge "pretty stable" by t
On Wed, Dec 06, 2017 at 12:25:14PM -0500, Eric S. Raymond via devel wrote:
> I have a different plan. I always write doc patches as part of my
> change commits; my discipline is to prevent code and docs from getting out
> of sync in the first place.
Does everyone on the project do that? This "p
Hal Murray :
> There was some sort of document on the release process. Anybody remember
> where it lives?
It's in devel/pre-release.txt. I think you wrote it.
> In the short term, I think we have 2 options. One is to make a bug fix
> release with only a few lines of code changed. That doesn
> Aha. This sounds like the beginning of something I just asked you to do
> privately - design an actual acceptance process for a release.
I'll be glad to work on that. Where does it fit in on the priorities? I'm
assuming not much will happen until after the release.
There was some sort of do
e...@thyrsus.com said:
> Well, normally it would be a longer freeze, but we're doing this to roll out
> a bug fix on code that has been pretty stable.
Your version of "pretty stable" doesn't match mine.
You want to make a point release to push out a one line patch. You are
dragging along all
Hal Murray :
> >From Subject: Re: Python 3 division
> > My plan is to let the current minor flurry of bug-fixing activity subside
> > and then call a short freeze.
>
> That's what I've been trying to complain about.
>
> If all you do is call a "short" freeze before a release, nobody ever has tim
On 10/06/2017 10:15 AM, Eric S. Raymond wrote:
This is why the minimal-change alternative is worth considering at this
point in our release cycle. It means you don't have to do that research
project.
Done, functions that can be simply changed to assertAlmostEqual have
been, problematic one
Ian Bruene via devel :
> I changed ntp_to_posix back to what it should be, and fixed what tests I can
> fix immediately.
Good.
> >A question for you to ponder: should you replace all assertEqual calls
> >or only those on which we have seen failures? If the latter, what
> >else do you need to do?
On 10/06/2017 06:52 AM, Eric S. Raymond wrote:
In fact, all this test code is subtly wrong, and it is just blind luck
nothing went sproing sooner. Any of those assertions could have gone
toes-up at any time. The tests in posixize() are wrong, too.
The problem here is that float representation
> I seem to recall that you were worried about your
> DNS-lookup changes slowing startup. Were you able to
> put that concern to rest?
I've assumed that any concerns about fast startup would avoid DNS.
We should compare new DNS, old DNS, and ntp classic with DNS.
--
These are my opinions. I h
Hal Murray :
> One of the things we need to verify is that our code starts as fast as ntp
> clsssic. I think they get going in 11 seconds. It's on their web someplace.
>
> I don't know how to easily automate that. A hack to scan log files might
> help.
Watching ntpmon, timing it to see when
On Fri, Feb 3, 2017 at 5:12 AM, Gary E. Miller wrote:
> I would want my installedcode to match my installed doc.
If you are editing only the docs (as I do), you may wish to rebuild the
docs after every commit to check.
Since waf is so fast, I just do a ./waf build anyway, so this is academic
f
Hal Murray :
>
> e...@thyrsus.com said:
> > That soumds like a request for two two different *install* productions.
> > Noted.
>
> I could easily imagine a rats-nest.
True, but that's orthogonal to whether it's a rat's nest at choice-of-config
time or a rat's nest at choice-of-install time.
>
e...@thyrsus.com said:
> That soumds like a request for two two different *install* productions.
> Noted.
I could easily imagine a rats-nest.
Why just two? How about a no-ntpviz option? How about a no-clients option?
The latter gets "interesting". I think there are two types of clients.
T
Hal Murray :
>
> >> --enable-doc-only doesn't build any documentation. :)
> > I think that is a silly option, and a perfect example of how the recipe got
> > overcomplicated. I'm going to remove it.
>
> How do I update the installed documentation without updating the code?
That soumds like a
> I would want my installedcode to match my installed doc.
I agree. But use your imagination.
The default is no doc. You have to turn on --enable-doc to get it. Suppose
I have done extensive testing with the installed code but forgot to turn on
--enable-doc. Why should I re-install the same
Yo Hal!
On Thu, 02 Feb 2017 13:03:24 -0800
Hal Murray wrote:
> >> --enable-doc-only doesn't build any documentation. :)
> > I think that is a silly option, and a perfect example of how the
> > recipe got overcomplicated. I'm going to remove it.
>
> How do I update the installed documenta
>> --enable-doc-only doesn't build any documentation. :)
> I think that is a silly option, and a perfect example of how the recipe got
> overcomplicated. I'm going to remove it.
How do I update the installed documentation without updating the code?
--
These are my opinions. I hate spam.
Hal Murray :
> --enable-doc-only doesn't build any documentation. :)
I think that is a silly option, and a perfect example of how the recipe
got overcomplicated. I'm going to remove it.
--
http://www.catb.org/~esr/";>Eric S. Raymond
__
Just pushed to devel/pre-release.txt
--
These are my opinions. I hate spam.
___
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.org/mailman/listinfo/devel
Sanjeev Gupta :
> I would prefer not renaming a document, it breaks search and explicit
> links.
For internal documentation (that is, not under docs/) I'm not really
willing to be bound by that kind of constraint. The moment we make
something public-facing, that changes.
--
http:
Sorry for the top post.
I would prefer not renaming a document, it breaks search and explicit
links.
On 13 Jan 2017 12:21 pm, "Eric S. Raymond" wrote:
> Hal Murray :
> >
> > e...@thyrsus.com said:
> > > I would be very grateful if you expanded this into a sufficiently
> detailed
> > > test pro
Hal Murray :
>
> e...@thyrsus.com said:
> > I would be very grateful if you expanded this into a sufficiently detailed
> > test protocol so that someone other than you can replicate the steps.
>
> I've got a start. What should we call it? There already exists
> devel/testing.txt which describ
e...@thyrsus.com said:
> I would be very grateful if you expanded this into a sufficiently detailed
> test protocol so that someone other than you can replicate the steps.
I've got a start. What should we call it? There already exists
devel/testing.txt which describes how to test ntpsec after
Hal Murray :
> We should start collecting a list of manual tests to run in preparation for a
> release or after a major change.
Agreed. Looks like you've made a good start on it.
> One obvious one is to make sure that all of the refclocks work. Some of them
> have several modes and options s
1 - 100 of 126 matches
Mail list logo
