Re: USE_PACKET_TIMESTAMP

2017-06-08 Thread Hal Murray via devel
Thanks for fixing this. Can you verify that it works as well as builds? > Newer versions of Solaris support SO_TIMESTAMP per: > https://docs.oracle.com/cd/E19957-01/820-0724/gcoqs/index.html That has a link to a setsockopt man page which says: SunOS 5.11 Last Revised 21 Jan 2007 It doesn't sa

Re: SolarisMime-Version: 1.0

2017-06-08 Thread Hal Murray via devel
> Can you please look at issue #343? Your commit broke the Solaris build. > https://gitlab.com/NTPsec/ntpsec/issues/342 I'll respond under the Re: USE_PACKET_TIMESTAMP thread. -- These are my opinions. I hate spam. ___ devel mailing list devel@nt

Re: Proposed argument changes to ntpq (fixing bug #319)

2017-06-08 Thread Eric S. Raymond via devel
Ian Bruene via devel : > > > On 06/08/2017 05:29 PM, Gary E. Miller via devel wrote: > >NTPsec does not use Python's getopt(). It uses argparse(). > > So the real alternatives here are: > > 1. Have the dual -l/-L flags > > 2. Convert ntpq from getopt to argparse Ian, I'm going to mutter that

Re: USE_PACKET_TIMESTAMP

2017-06-08 Thread Gary E. Miller via devel
Yo Matthew! On Thu, 8 Jun 2017 20:47:51 -0400 Matthew Selsky via devel wrote: > Newer versions of Solaris support SO_TIMESTAMP per: So why does the compile failt on buildbot? Is buildbot on an old version? RGDS GARY --- G

Re: USE_PACKET_TIMESTAMP

2017-06-08 Thread Matthew Selsky via devel
On Thu, Jun 08, 2017 at 12:26:21AM -0700, Hal Murray via devel wrote: > Can anybody confirm that Solaris really doesn't have time stamps? I thought > we decided that all modern OSes did. That's why we could rip out the SIGIO > stuff. > > I took a quick google and couldn't find any mention of a

✘Solaris ?

2017-06-08 Thread Gary E. Miller via devel
Yo Hal! Can you please look at issue #343? Your commit broke the Solaris build. https://gitlab.com/NTPsec/ntpsec/issues/342 RGDS GARY --- Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703 g...@r

Re: Proposed argument changes to ntpq (fixing bug #319)

2017-06-08 Thread Gary E. Miller via devel
Yo Ian! On Thu, 8 Jun 2017 17:34:27 -0500 Ian Bruene via devel wrote: > On 06/08/2017 05:29 PM, Gary E. Miller via devel wrote: > > NTPsec does not use Python's getopt(). It uses argparse(). > > So the real alternatives here are: > > 1. Have the dual -l/-L flags Yuck. Non orthogonal to nt

Re: Proposed argument changes to ntpq (fixing bug #319)

2017-06-08 Thread Ian Bruene via devel
On 06/08/2017 05:29 PM, Gary E. Miller via devel wrote: NTPsec does not use Python's getopt(). It uses argparse(). So the real alternatives here are: 1. Have the dual -l/-L flags 2. Convert ntpq from getopt to argparse -- In the end; what separates a Man, from a Slave? Money? Power? No. A

Re: ntpsec | ntpq: -d -d != -D2 (#319)

2017-06-08 Thread Gary E. Miller via devel
Yo Ian! On Thu, 8 Jun 2017 17:31:01 -0500 Ian Bruene via devel wrote: > On 06/08/2017 05:18 PM, Gary E. Miller via devel wrote: > > So, what do you think is still unresolved? > > At this point I think we have solved it, simply by eliminating the > alternatives. It's all part of the ntpq fla

Re: ntpsec | ntpq: -d -d != -D2 (#319)

2017-06-08 Thread Ian Bruene via devel
On 06/08/2017 05:18 PM, Gary E. Miller via devel wrote: So, what do you think is still unresolved? At this point I think we have solved it, simply by eliminating the alternatives. It's all part of the ntpq flag discussion. -- In the end; what separates a Man, from a Slave? Money? Power? N

Re: Proposed argument changes to ntpq (fixing bug #319)

2017-06-08 Thread Gary E. Miller via devel
Yo Ian! On Thu, 8 Jun 2017 15:29:19 -0500 Ian Bruene via devel wrote: > >> "A (':') shall be returned if getopt() detects a missing > >> argument and the first character of optstring was a (':')." > >> > >> So optional optarg can be valid POXIX. > > I didn't know that. Thanks. > > Unfort

Re: ntpsec | ntpq: -d -d != -D2 (#319)

2017-06-08 Thread Gary E. Miller via devel
Yo Ian! On Thu, 08 Jun 2017 20:27:50 + Ian Bruene wrote: > The "DNS[...]" bug is fixed in !483, the rest of the fix requires > change in the debugging flags. Once some sort of agreement is arrived > at on the devlist. So, what do you think is still unresolved? RGDS GARY ---

Re: Proposed argument changes to ntpq (fixing bug #319)

2017-06-08 Thread Ian Bruene via devel
On 06/08/2017 02:48 PM, Eric S. Raymond via devel wrote: Gary E. Miller via devel : Well, more to be learned, my getopt(3p) is not the same as what I see on unix.com. The online copy did not include the snippet I quoted. You can confirm on the POSIX site for getopt(3P): http://www.unix.com/

Re: Proposed argument changes to ntpq (fixing bug #319)

2017-06-08 Thread Eric S. Raymond via devel
Gary E. Miller via devel : > Well, more to be learned, my getopt(3p) is not the same as what I see on > unix.com. The online copy did not include the snippet I quoted. You > can confirm on the POSIX site for getopt(3P): > > http://www.unix.com/man-page/posix/3p/getopt/ > > But they both had thi

Re: USE_PACKET_TIMESTAMP

2017-06-08 Thread Eric S. Raymond via devel
Hal Murray : > > >> If Solaris doesn't support time stamps, I would expect > >> ntp_packetstamp to die on a #error. What happened with it? > > > I factored the code so that if waf configure doesn't find a way to get > > packet arrival times from the UDP layer it uses the arrival time collected >

Re: USE_PACKET_TIMESTAMP

2017-06-08 Thread Hal Murray via devel
>> If Solaris doesn't support time stamps, I would expect >> ntp_packetstamp to die on a #error. What happened with it? > I factored the code so that if waf configure doesn't find a way to get > packet arrival times from the UDP layer it uses the arrival time collected > in userspace (ntp_packet

Re: Proposed argument changes to ntpq (fixing bug #319)

2017-06-08 Thread Gary E. Miller via devel
Yo Eric! On Thu, 8 Jun 2017 15:01:55 -0400 "Eric S. Raymond" wrote: > Gary E. Miller via devel : > > Yo Eric! > > > > On Wed, 7 Jun 2017 22:46:42 -0400 > > "Eric S. Raymond" wrote: > > > > > Gary E. Miller via devel : > > > > Just make the filename optional. So -l or -l filename > > >

Re: USE_PACKET_TIMESTAMP

2017-06-08 Thread Eric S. Raymond via devel
Hal Murray via devel : > Can anybody confirm that Solaris really doesn't have time stamps? I thought > we decided that all modern OSes did. That's why we could rip out the SIGIO > stuff. > > I took a quick google and couldn't find any mention of anything that looked > like a time stamp in a S

Re: Proposed argument changes to ntpq (fixing bug #319)

2017-06-08 Thread Eric S. Raymond via devel
Gary E. Miller via devel : > Yo Eric! > > On Wed, 7 Jun 2017 22:46:42 -0400 > "Eric S. Raymond" wrote: > > > Gary E. Miller via devel : > > > Just make the filename optional. So -l or -l filename > > > > Sadly, not practical with any varint of C or Python getopt. We'd have > > to roll our own

Re: Proposed argument changes to ntpq (fixing bug #319)

2017-06-08 Thread Ian Bruene via devel
On 06/08/2017 03:22 AM, Hal Murray wrote: If you are looking at ntpq, it would be nice if there was a simple way to see the packets sent/received and not much else. A few of the packets have binary data. It may be as simple as only assoc IDs are in binary. Everything else is raw ascii so it

Re: Proposed argument changes to ntpq (fixing bug #319)

2017-06-08 Thread Hal Murray via devel
If you are looking at ntpq, it would be nice if there was a simple way to see the packets sent/received and not much else. A few of the packets have binary data. It may be as simple as only assoc IDs are in binary. Everything else is raw ascii so it doesn't need any complicated parsing or re

Re: USE_PACKET_TIMESTAMP

2017-06-08 Thread Hal Murray via devel
Can anybody confirm that Solaris really doesn't have time stamps? I thought we decided that all modern OSes did. That's why we could rip out the SIGIO stuff. I took a quick google and couldn't find any mention of anything that looked like a time stamp in a Solaris man page for setsockopt. Bu

Re: Proposed argument changes to ntpq (fixing bug #319)

2017-06-08 Thread Gary E. Miller via devel
Yo Eric! On Wed, 7 Jun 2017 22:46:42 -0400 "Eric S. Raymond" wrote: > Gary E. Miller via devel : > > Just make the filename optional. So -l or -l filename > > Sadly, not practical with any varint of C or Python getopt. We'd have > to roll our own, and that way madnes lies. man geetopt: "If