After a great deal of refactoring, digging, confusion, and generalized
wrestling with the surprising number of tentacles that comprise the
mrulist system I can now make a report of sorts:
*Error handling expected by the protocol:*
* If there is no overlap between the requested entries and
On 11/20/19 5:44 PM, Hal Murray via devel wrote:
Part of the problem is that there is a lot of cruft in that area. For
example, grep for CERR_
There is a clump of signals defined as part of a ControlSession, none are ever
raised, a few are caught. Looks like somebody decided to rename things
On 8/29/19 4:36 PM, Gary E. Miller via devel wrote:
Hal you are corect. Page 140, section 6.7.9 Initialization.
"If an object that has static or thread storage duration is not initialized
explicitly, then:
[...]
-- if it has arithmetic tye, it is initialized to (positive or unsigned)
zero;"
On 8/29/19 3:46 PM, Eric S. Raymond wrote:
By "floating", you mean uninnitialized? In C that's going to mean it's false
Yes. My understanding of C is that anything not explicitly set has
whatever random value happens to be in that memory location. Possibly
changed if certain unknown
The other day I determined that the flag disable_dynamic_updates
(currently in the io_data struct) is either not properly initialized, or
is blocking off a large chunk of dead code. After reading through the
relevant code and looking through the history I think it is the former:
The flag is
On 8/28/19 1:26 PM, Hal Murray wrote:
Merge Request !1026 was merged
The Subject says "Converted stat_count struct to a module level global"
The code looks like it is un-struct-ing things.
Was that "a module level global" supposed to be "module level globals"?
!1026 moves the variables
Question obsolete; I was mixing up some details.
On 6/30/19 12:35 PM, Ian Bruene wrote:
I have been trying to write tests for the NTS packet extension code in
nts_extens.c. Almost all of the functions end up needing to encrypt or
decrypt something. It is simple enough to feed in random data
I have been trying to write tests for the NTS packet extension code in
nts_extens.c. Almost all of the functions end up needing to encrypt or
decrypt something. It is simple enough to feed in random data for
encryption, but for decryption the various keys and other data needs to
match up.
Nevermind: I figured out what I failed to understand.
The handlers that use CMAC and are size locked are on the client to
server path. The server to client path *does* allow for additional data.
Nothing to see here, move along.
--
/"In the end; what separates a Man, from a Slave? Money?
On 6/23/19 4:09 PM, Daniel Franke wrote:
The translation of the AEEF ciphertext into corresponding plaintext is
given by the negotiated AEAD algorithm; for AES-SIV, by RFC 5297. The
structure of the plaintext is defined in the draft, as a concatenation
of RFC 7822 extension fields.
This
While working on the NTS test code I have reached a point where I know
that I am misunderstanding *something*, but do now know what.
According to the RFC the AEEF "ciphertext" field looks like it is a
generally usable data blob for extension data. Variable size, no
specific data, etc.
On 6/19/19 5:28 PM, Eric S. Raymond via devel wrote:
I'd like to see two different kinds of responses to this provocation.
1. Are there blockers on the road to Go?
2. No, there's something else more important to do first.
Before any general push to Go happens there needs to be either a
On 6/16/19 7:47 AM, Eric S. Raymond via devel wrote:
Yes, a triage run is near the top of my to-do list. Expect to see some results
on that by midweek.
Do you cansider the NTS documentation to be in good shape?
I have a branch with a large number of NTS tests that has been sitting
in
On 4/23/19 9:47 PM, Gary E. Miller via devel wrote:
And that is how cruft grows...
I only disabled them at the time of my test push because I didn't
understand what they were. With that understanding I can now remove them
entirely.
--
/"In the end; what separates a Man, from a Slave?
The hack worked.
On 4/23/19 9:31 PM, Hal Murray via devel wrote:
There is at least one other place where the test routines have a routine to
keep the linker happy, but I can't think of what it is.
When it was mentioned I remembered seeing that in the nts.c tests.
Ironically I had to
In trying to write tests for nts_client.c I have run into a problem I do
not know how to solve, as it involved much of the structure of the
codebase as well as the build system.
Some of the code in nts_client.c calls the dns_take* series of
functions. These functions are defined in
On 4/1/19 12:00 AM, Hal Murray via devel wrote:
There is some cleanup I've wanted to do in that area anyway. I'll try to get
to it tonight.
Noted, will wait before stirring it up.
Only that it seemed reasonable at the time. I was more interested in getting
things working than how to test
After staring at the code for long enough I see a number of natural
cleavage points for solving this issue. MR in a few days.
On 3/31/19 2:33 PM, Ian Bruene wrote:
Is there any particular reason why SSL structs need to be passed all
over the place to functions that do not depend on SSL
Is there any particular reason why SSL structs need to be passed all
over the place to functions that do not depend on SSL itself?
The notable example here is nts_ke_do_recieve, which only uses the SSL
to pass to SSL_read. I don't see any obvious reason that couldn't be
done in the calling
On 3/2/19 9:42 AM, Eric S. Raymond via devel wrote:
REFCLOCKD benefits way down, cost almost unchanged. Every time I model
this in my head the same answer comes out: bad idea. I think we have
better complexity-reduction attacks available, like translating the
whole thing to Go to get rid of a
After looking at the cookie creation code I don't understand how a
server is supposed to extract the keys contained within. It would not
have the data to de-xor the contents of the cookie when presented with
said cookie.
Unless this is just a placeholder?
int make_cookie(uint8_t *cookie,
Someone wondered what the changes in draft 16 were. Aside from date
update miscellanea the only change is in section 9.3.
This paragraph:
Do not process time packets from servers if the time computed from
them falls outside the validity period of the server's
certificate.
On 2/1/19 3:53 PM, Eric S. Raymond via devel wrote:
What is the natural kind in which "nts" is an alternative to "server",
"pool", and "refclock"? If there is such a kind, how does that square
with the possibility that "nts" may become a property of pool request
instances?
Possibly if nts
*Ahem* R...
You are both talking past each other.
There are two key sets:
The c2s/s2c pair. Generated *BY* the TLS exchange between the client and
the NTS-KE server. Stored inside the cookie. Used to encrypt data
between server and client NTPDs thereby eliminating the need for a
On 1/17/19 7:11 PM, Hal Murray via devel wrote:
Do both NTP-server and NTS-KE-server have to know the new-cookie recipe? Does
NTS-KE-server need the master key for anything other than generating cookies?
Does it work if only the NTP-server has the master key and the NTS-KE-server
gets cookies
On 1/17/19 2:00 PM, Eric S. Raymond wrote:
Ian Bruene via devel :
Charlie requests a master key (and possibly initial cookies) daily
from Delta.
Cookies wouldn't be part of that. For a start "once a day" would have the
cookies up to tens of thousands of packets out of date (assumin
On 1/17/19 11:35 AM, Eric S. Raymond via devel wrote:
I see no Bravo-to-Alpha initiation of requests, though there are
responses heading in that direction.
I think everyone has been treating Alpha and Bravo as the same entity.
Similarly, I see no Delta-to-Bravo initiation of requests,
I know of these keys that exist within NTS:
* client-to-server (c2s)
* server-to-client (s2c)
* server master key
The master key is shared between NTPD and NTS-KE (mechanism currently
undecided). It is used to encrypt data in cookies and is never seen
outside of the NTPD/NTS-KE pair. *The
On 01/06/2019 05:11 PM, Gary E. Miller via devel wrote:
Which is a big doc, so I'm still not sure which part we are talking
about here...
/devel/nts.doc is a new, and currently very small, file.
You are thinking of the NTS draft.
That is a bad way to think of this. What you call
On 01/06/2019 04:57 PM, Gary E. Miller via devel wrote:
That is the one option that has been universally shot down as bad.
I'm not sure what option you refer to. Best in discussions like these to
keep indirection to a minimum.
The one I had just been talking about as being implied by the
On 01/06/2019 02:55 PM, Gary E. Miller via devel wrote:
Seems to me that Section 6 of the proposed RFC defines this pretty well.
Once you can figure out who Clarlie (NTPD) and Delta (NTS-KE) are.
Partially. It gives an example of a way to do it, but no protocol or
message scheme; just what
Fwd because I hit the wrong reply button.
Forwarded Message
Subject:Re: Let's get moving on NTS
Date: Sun, 6 Jan 2019 14:20:25 -0600
From: Ian Bruene
To: Eric S. Raymond
On 01/06/2019 01:38 PM, Eric S. Raymond via devel wrote:
So I think my job for the
On 10/31/18 6:08 AM, Ian Bruene wrote:
While waiting for the NTS holding pattern I'm going to take another
look at the recvbuff removal.
It seems that I missed where SINGLEBUFFER already happened. Taking a
poke at the python code instead; maybe there is some cleanup that can
happen
While waiting for the NTS holding pattern I'm going to take another look
at the recvbuff removal.
--
/"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. It will exist the moment we are fit
On 10/31/18 2:07 AM, Eric S. Raymond wrote:
Ian Bruene via devel :
On 10/30/18 3:32 PM, Mark Atwood, Project Manager via devel wrote:
Looks straightforward enough. Ian?
Will look into in a little while.
Invoke me if you run into trouble, but this should be pretty sreaightforward.
Gary
On 10/30/18 3:32 PM, Mark Atwood, Project Manager via devel wrote:
Looks straightforward enough. Ian?
Will look into in a little while.
--
/"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
I'm told that there is a document written by the resident crypto expert
describing NTS. Does anyone have it? We might need to see it if we are
planning on implementing what is in it you know...
--
/"In the end; what separates a Man, from a Slave? Money? Power? No. A
Man Chooses, a Slave
On 09/17/2018 04:53 PM, Hal Murray via devel wrote:
If they are written in Go, they are compiled to binary executables, and you
do not need Python (nor a Go compiler) to run them.
Thanks. But we still need libraries. What makes the Python
interpreter/whatever different from a library?
Go
On 09/17/2018 12:34 PM, Eric S. Raymond via devel wrote:
2. PYTOGO
We now have a goal of moving all our client-side code from Python to Go.
Benefits: (1) banish the horror that is Python library directories, (2)
remove a run-time dependency for operators, (3) build competence and
On 09/14/2018 01:21 PM, John D. Bell via devel wrote:
This is a test message to the mailing list, to diagnose apparent
failure to deliver, etc.
It can safely be ignored.
Pong
--
/"In the end; what separates a Man, from a Slave? Money? Power? No. A
Man Chooses, a Slave Obeys."/ --
(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. It will exist the moment we are fit
to occupy it."/ -- Sophia Lamb
I work for the Internet Civil Engineering Institute
On 08/31/2018 09:44 AM, Ian Bruene wrote:
On 08/30/2018 11:50 PM, Gary E. Miller via devel wrote:
Oh, most certainly on shutdown.
Do you have a recipe to reproduce? Or does it happen every time?
So far I have not been able to reproduce this on my system. Still digging.
--
/"In the end;
On 08/30/2018 11:50 PM, Gary E. Miller via devel wrote:
Oh, most certainly on shutdown.
Do you have a recipe to reproduce? Or does it happen every time?
--
/"In the end; what separates a Man, from a Slave? Money? Power? No. A
Man Chooses, a Slave Obeys."/ -- Andrew Ryan
/"Utopia cannot
Fwd due to Reply/Reply all mistake.
On 08/29/2018 01:26 PM, Eric S. Raymond via devel wrote:
Those projects do tend to blur tigether in my mind.
You were planning to do quue removal at one point. Is that still on
your list?
I've poked at both of those over the last couple months, didn't
Forwarded because wrong reply target
Forwarded Message
Subject:Re: Preparing for upcoming release
Date: Mon, 13 Aug 2018 14:36:27 -0500
From: Ian Bruene
To: Eric S. Raymond
On 08/13/2018 02:34 PM, Eric S. Raymond via devel wrote:
So, core devs:
On 06/20/2018 01:52 PM, Matthew Selsky wrote:
Is there a way to have Unity spit out information on test coverage percentage?
If so, tell me how and I'll take a look at wiring it into our gitlab CI.
Unfortunately I know almost nothing about Unity.
--
/"In the end; what separates a Man,
I said:
On 06/19/2018 07:02 PM, Ian Bruene wrote:
Also at least one test file is misnamed.
I will go through these and check / patch everything to be where it
should be
I need to sanity check this first: Am I correct in thinking that tests
should be arranged as 1 file of tests
I had a look through libntp/ and tests/libntp/ today.
Of the 35 files that are relevant for testing
* 4 are AFAICT fully tested
* 11 have partial tests
* 20 do not even have a test file
There is undoubtedly some error in these figures as the test directory
has some files in it that do not
On 06/18/2018 03:37 PM, Eric S. Raymond via devel wrote:
Ah, now that's the kind of error pattern I *expect* from Bison parsers.
The underlying problem is that the C in Bison parser skeletons is
really archaic. It dates from times when not even the value of
procedural encapsulation was fully
On 05/30/2018 02:45 PM, Hal Murray via devel wrote:
It can be done in two steps. First is to dump the work-queue but still make
each packet get a buffer from the free queue and go back there. The second
is to remove the free queue.
Looking at the code, I believe this is the proper action
On 05/29/2018 03:54 PM, Eric S. Raymond wrote:
Ian Bruene via devel :
I've skimmed through some of the code associated with these features during
deglobalization. It /needs/ to be cleaned up one way or another. Cleaning it
with a scythe is all the better.
Hmmm. You may have talked yourself
On 05/29/2018 02:15 PM, Eric S. Raymond via devel wrote:
I'm inclined to think dropping this would be a good thing. There's a
lot of code complexity behind that, and that bit abour interface
commands being inoperative if you choose the wrong command-line option
raises my shoot-self-in-foot
On 05/27/2018 01:56 PM, Hal Murray via devel wrote:
How thread friendly is GO?
Very. Easy concurrency in network software is Go's major raison d'être.
--
/"In the end; what separates a Man, from a Slave? Money? Power? No. A
Man Chooses, a Slave Obeys."/ -- Andrew Ryan
/"Utopia cannot
On 05/27/2018 11:31 AM, Eric S. Raymond via devel wrote:
* GOPREP: Clear the path to moving the codebase to Go. We haven't committed
to doing this yet, but the odds on that happening someday look high enough
that I think it is good to already be factoring it into our planning.
Though it is
I have done a scan over the variables that I have already structified in
recent weeks to see where they get initialized.
Most of the variables I have checked get initialized either at
definition time, or in some sort of init_foo() function. I found three
variables that are never
The Southeast Linux Fest will be June 8-10th. It appears that 1.2 is
scheduled for June 15th.
Would it not be better to schedule it for the 5th or so, giving room for
a couple days delay while still being able to say "We just shipped 1.2"
at SELF?
--
/"In the end; what separates a Man,
On 03/15/2018 02:35 PM, Jason Azze via devel wrote:
Sanjeev, was this template created in response to your bounty? I
finally worked through getting ntpsnmpd up and talking to AgentX on my
test machine, but all of my Cacti graphs from netniV's template come
up NaN.
Ian, could you recommend
On 03/09/2018 12:43 PM, Mark Atwood, Project Manager via devel wrote:
Ok, trying again. We held the 1.0.1 release for a fix for a problem
that Hal discovered and fixed. Thank you, Hal!
Since we have a CVE fix in this release, and also a "make it work
better on AWS AMIs" fix in, I do want
On 03/02/2018 03:47 PM, Hal Murray via devel wrote:
It wouldn't surprise me if we had added something interesting. I'm pretty
sure I have added things. The only question is did we fill in a gap in
classic and/or will ntpsnmpd do the right thing if it encounters something
like that.
On 03/01/2018 07:40 PM, Hal Murray via devel wrote:
Mark Atwood said:
ntpsnmpd should be it's own Debian package, please. It's useful to both
NTPsec and to NTP Classic installations.
Has anybody tried it with NTP Classic? Do we have a classic server running
that we can test against?
On 02/26/2018 06:13 PM, Sanjeev Gupta via devel wrote:
Hi,
For what it is worth, I am running the ntpsnmpd code on a number of
debian and ubuntu machines for some time, including one with an actual
GPS. No issues so far.
I just like to see graphs.
Hooray! Someone is using the code!
1.
ntpsnmpd is now fully part of the build. Manpage installs properly.
make-tarball includes it (mostly because it slurps up everything).
--
/"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.
On 02/25/2018 07:18 PM, Hal Murray via devel wrote:
Is there a HOWTO that tells me how to set things up?
I'll get to work on that.
There may be two targets for that document. One is SNMP wizards who don't
know much about ntpd. The other is NTP wizards who don't know much about
SNMP.
On 02/26/2018 09:50 AM, Mark Atwood via devel wrote:
Does waf build it by default?
Does the Debian packaging have it be it's own package?
It is built as part of the other python utilities. The manpage isn't
part of the build yet as I do not know which section it should go in.
--
/"In the
On 02/25/2018 04:39 PM, Hal Murray via devel wrote:
devel@ntpsec.org said:
The only real blocker that I can see at this time is the need for broad
testing. [reiteration of me requesting testers / reviewers goes here.]
Is there a HOWTO that tells me how to set things up?
I'll get to work on
On 02/25/2018 04:43 PM, Eric S. Raymond via devel wrote:
Gary E. Miller via devel <devel@ntpsec.org>:
On Sun, 25 Feb 2018 16:02:00 -0600
Ian Bruene via devel <devel@ntpsec.org> wrote:
[...]
OTOH, people will not test it until it is easy to test. So I'd suggest
putting
Is ntpsnmpd having it's Official Release with 1.0.1, or are we punting
to the next release?
Right now I do not believe that it would be crazy, but there are still
options that need work, and logging is not systematic and consistent
yet. The missing options I've thought of are all simple to
Future project: refactoring ntpd's system variables into a struct.
I've been looking at the code around mode 6 generation and discovered
that in some areas it's still globals all the way down. Translating
these globals will make future refactoring/translating easier.
--
/"In the end; what
On 02/20/2018 08:41 PM, Mark Atwood via devel wrote:
Hi!
A few months ago, I announced prep for a 1.0.1 release. Turns out, it never
actually happened.
So, I'm declaring an intention for the 1.0.1 release the weekend after next,
about March 3rd.
As you work, consider stability, and avoid
On 02/20/2018 09:19 PM, Eric S. Raymond via devel wrote:
I'll get on the tracker and swat a bunch of small issues I see.
The big deal is whether we have closure on the Python installation mess.
The Python installation works the way it did before that last minute
'fix' before 1.0. So the
On 02/16/2018 02:17 PM, Hal Murray via devel wrote:
Is there a client for ntpsnmpd? I'd expect the client side to be part
of a snmp package. Do we need samples for that? How many snmp packages
are there?
ntpsnmpd only talks to the snmpd daemon. Various sorts of clients,
including the
Rellim
To: Ian Bruene <ianbru...@gmail.com>
Yo Ian!
On Fri, 16 Feb 2018 11:03:36 -0600
Ian Bruene via devel <devel@ntpsec.org> wrote:
Query: what file can/should I use for config data that ntpsnmpd needs
to be able to change on the fly?
You think it will be that simple? :-
On 02/16/2018 01:09 PM, Eric S. Raymond wrote:
Ian Bruene via devel <devel@ntpsec.org>:
Query: what file can/should I use for config data that ntpsnmpd needs to be
able to change on the fly?
Does a human ever set this data? If not, there's a (weak) convetion of
putting the file in /v
Query: what file can/should I use for config data that ntpsnmpd needs to
be able to change on the fly?
--
/"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. It will exist the moment we are
MIB implementation complete except for where explicitly not implemented.
No known bugs extant, mostly due to lack of swarm attack.
Packet handling implemented for all required PDU types. But not all in
general.
Can has testers?
--
/"In the end; what separates a Man, from a Slave? Money?
On 02/13/2018 04:23 PM, Hal Murray wrote:
devel@ntpsec.org said:
From the possible values of ntpEntStatPktMode it would appear that the
"modes" this table is talking about are not the normal NTP communication
modes like mode6.
What are the possibilies?
From the MIB:
ntpEntStatPktMode
Returning to work on ntpsnmpd after a hiatus I looked through the MIB
entries and discovered that I had accidentally skipped one of the tables.
The table is described as "The number of packets sent and received by
packet mode. One entry per packet mode.".
It has 3 fields per mode:
On 02/01/2018 11:22 AM, Mark Atwood, Project Manager wrote:
The SNMP MIB RFCs are notorious for including magic blue sky values
and measurements that nobody knows how to measure and that are not
well defined.
For things that don't make enough sense, it's ok to not implement that
particular
I finally tracked down where root_distance is created. ntpd/ntp_proto.c
line 2130 function root_distance.
However it is a function internal to ntp_proto.c, not mentioned in
header files. And as far as I can tell the values generated from it are
only ever used inside the functions in that
Accidentally replied to ESR directly instead of the list
Update on previous status.
On 01/09/2018 11:42 AM, Eric S. Raymond wrote:
Heads up, Hal! I'd like your opinopn on these.
Ian Bruene via devel<devel@ntpsec.org>:
* Time Resolution (not to be confused with Time /Precision/,
First proposal: For cases where a piece of code needs to embed brittle
assumptions, in addition to the comment block explaining said
assumptions it should also include a HAZARD tag with a one line summary
(not unlike a git summary line). While this standard will only help to
catch instances
On 01/09/2018 11:42 AM, Eric S. Raymond wrote:
Third way: there's a reference to get_resolution() ntp_systime.c at
line 147 ("After default_get_precision() has set a nonzero sys_fuzz")
that implies two things; (1) get_resolution() used to be called within
ntpd, and (2) its role has been taken
On 01/09/2018 09:58 AM, Jason Azze via devel wrote:
At the risk of sounding like a drop-out from a Scrum Master training
camp, could you explain briefly what the "story" is for this tool?
I use SNMP every day to monitor the health of lots of servers and
services, but, to be honest, I haven't
On 01/08/2018 05:30 AM, Hal Murray via devel wrote:
This smells like a Gitlab glitch, probably transient.
Is there a simple way to say "Please try again?" (without adding clutter to
git's log)
Click the pipeline icon, there will be options from there.
--
/"In the end; what separates a Man,
This is a summary of the last few months of intermittent arguing over
the build system. I am glossing over most details as the specifics are
not important to the summary, and I'm too lazy to track down every post
on the matter.
Just before the 1.0 release Fred Wright submitted a patch to
How can I get a detailed report on the new python test coverage check?
And how robust is it: does it only count the percentage of functions
tested, or can it tell what parts of a function are being exercised?
91% is higher than I expected.
--
/"In the end; what separates a Man, from a
On 01/04/2018 10:48 PM, Richard Laager via devel wrote:
Can you submit an actual merge request for review?
Currently waiting for the pipeline to finish on !641.
This changes the build back to how it used to work, it builds and
installs on my system, it has passed the build phase of the
Oy Gary!
I think on a a couple of your responses we may be talking about
different things. However that is moot at this point, as it is clear
that we have our last solution standing: rip out the "fix" that started
this whole debate and revert to the old method.
--
/"In the end; what
On 01/04/2018 01:21 PM, Gary E. Miller via devel wrote:
What are these other issues?
The FHS, Gentoo, and AFAIK all distros, do not include /usr/local/XX
in any enviroment PATHs.
Ubuntu does. Did people just not usually use /usr/local/ much in the
Eldar Days? That would explain it not
On 01/04/2018 12:54 PM, Gary E. Miller via devel wrote:
[*SNIP* long description of why path embedding is Not Done]
RGDS
GARY
Ah. This was rattling around in the back of my head but I had forgotten
the details. !615's fix can be removed from consideration.
--
/"In the end; what separates
On 01/04/2018 11:44 AM, Richard Laager via devel wrote:
I'm not convinced it's actually bad form. Can you elaborate on why you
see this as hideous?
My understanding is that embedding paths into code like this is
something that Shouldn't Be Done unless absolutely necessary. It also
adds the
Uh, news to me that any solution was agreed to. Last I heard this
group was in no way on the same page.
Rather than having me misread your code, can you put a plain summary here?
It's rlaager's code, the bash sys.path in each program one.
Not sure how that makes me feel better. Exactly
We are on track to merging the solution in !615, if you have objections
please state them *soon*, together with a patch that fixes the problem.
We are rapidly approaching the planned mid-January 1.1 date.
To snip one large set of objections in the bud: Yes, this solution is
/hideous/.
I have started implementing notification support in ntpsnmpd, however I
have been unable to get it working so far. I do not believe there is an
error in the packet encoding, but there must be a problem somewhere in
my code as the master agent only ever returns responses with error 268
On 12/12/2017 08:04 PM, Hal Murray via devel wrote:
Something broke in my setup and I can't figure out what's going on.
Er, whoops! I broke that as part of my fix for improperly generated
files. Should be fixed now.
--
/"In the end; what separates a Man, from a Slave? Money? Power? No. A
On 12/10/2017 04:26 PM, Ian Bruene wrote:
On 12/10/2017 10:52 AM, Eric S. Raymond wrote:
Do you understand the problem well enough that you could specify an upstream
fix?
I'm not yet certain whether python or the distributions have
jurisdiction here. Earlier comments from rlaager suggest
On 12/10/2017 10:52 AM, Eric S. Raymond wrote:
Ugly, but simple. I'd like to hear counterargument from Gary and Fred before
we make a final decision. Keep it succint, guys.
Agreed. My main concern is that trying to be clever here has many ways
to go wrong, and few ways to detect them
After reading over the discussion regarding the recent /issues/, I have
come to a side: Revert Fred's fix and throughly document the import
breakage.
Reasoning:
The standard method means that on some systems the ntp module can't be
seen by python without modifying PYTHONPATH.
The fix
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
On 12/06/2017 09:11 AM, Richard Laager via devel wrote:
Probably? The behavior was already correct for the distro package. Was
anything else broken?
For installs the only remaining problem is that for unknown reasons it
sometimes doesn't follow the PREFIX when installing the python libs.
1 - 100 of 149 matches
Mail list logo
