devel@ntpsec.org said:
> If you are going to always #undef SO_BINTIME, why a few lines later test for
> it? Some left over test code?
Because I didn't know if SO_BINTIME for IPv6 was really broken on FreeBSD or
there was something simple I could do to make it work.
The #undef kludge made thin
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.
--
http://www.catb.org/~esr/";>Eric S. Raymond
Please consider contributing to my Pa
On Thu, Jun 8, 2017 at 7:11 AM, Gary E. Miller via devel
wrote:
> > Sanjeev, keep those servers mothballed, unless you have a personal
> > itch make hpux work.
>
> Oh, I hope not... Give them to a museum, if they'll take them...
Gary, the critical word there is "if". How do you think I landed
Yo Ian!
On Wed, 7 Jun 2017 19:02:49 -0500
Ian Bruene wrote:
> ntp*q*
Sorry, my mistake. I read 'ntpd'. But still try to keep the
options the same as possible.
RGDS
GARY
---
Gary E. Miller Rellim 109 NW Wilmington Ave.,
Yo Ian!
On Wed, 7 Jun 2017 18:31:15 -0500
Ian Bruene via devel wrote:
> Currently ntpq has -d and -D flags which function much like the ones
> for ntpd. Except that the -d flag also sets ntpq to log to a file
> instead of stderr because, um, reasons?
Evolution is hard to understand, much less m
Currently ntpq has -d and -D flags which function much like the ones for
ntpd. Except that the -d flag also sets ntpq to log to a file instead of
stderr because, um, reasons?
Proposed interface change:
-d/-D remain, but *only* affect the debug level
Add flag -l / --log-file (alt: -f, etc)
Yo Hal!
I'm confused by commit 7bb7a656cbabd4be451d35c6a6058fac9ca8a56d.
This new code in ntp/ntp_timestamp.c line 38:
-
#ifdef SO_BINTIME
/* SO_BINTIME doesn't work for IpV6, FreeBSD 11, 2017-Jan
* fortunately, FreeBSD also supports SO_TI
Yo Mark!
On Wed, 07 Jun 2017 06:55:07 +
Mark Atwood wrote:
> Hilariously, I don't know where we can get a HPUX lab machine.
Don't ask, we don't want to know...
> I want to support it, but I also want us to stick to "POSIX only,
> unless it's really important".
I'm happy with POSIX only.
Yo Hal!
commit a893edc7fa5fdf05b7558c46b2e83db9c7a0881b broke Solaris.
Buildbot shows a build failure.
New issue here:
https://gitlab.com/NTPsec/ntpsec/issues/342
Solaris has no msg_flags, msg_control or msg_controllen in struct
msghdr. The last two are key to what that function does.
You'
ok, kill that code.
Sanjeev, keep those servers mothballed, unless you have a personal itch
make hpux work.
..m
On Wed, Jun 7, 2017, 1:25 AM Eric S. Raymond wrote:
> Sanjeev Gupta via devel :
> > I am not sure that there will be any Sysadmins who will install NTPSec on
> > HPUX, the few installa
Sanjeev Gupta via devel :
> I am not sure that there will be any Sysadmins who will install NTPSec on
> HPUX, the few installations I know are strictly in "do not touch, very
> important business application running, last guy who understood this left
> three years ago".
I share your skepticism.
--
Mark Atwood via devel :
> Hilariously, I don't know where we can get a HPUX lab machine.
>
> I want to support it, but I also want us to stick to "POSIX only, unless
> it's really important".
>
> How much HPUX only code is there? What does it do?
I didn't think there was any left (I thought I'd
On Wed, Jun 7, 2017 at 2:55 PM, Mark Atwood via devel
wrote:
> Hilariously, I don't know where we can get a HPUX lab machine.
I have two (mothballed) HP Integrity servers, Itanium architecture. I
think they have HPUX installed.
If there is interest, I can power on, and turn over to whoever is
> That is worth filing a bug against BSD for.
They have confirmed that they know about it. (rather than I was confused)
--
These are my opinions. I hate spam.
___
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.org/mailman/listinfo/devel
14 matches
Mail list logo
