Eric S. Raymond
esr at thyrsus.com
Wed Jun 7 08:24:37 UTC 2017
Mark Atwood via devel <devel at ntpsec.org>:
> 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 removed it all), but
upon close examination I find there is one obscure conditional in the
ISC code. It, and the code it guards.
Here's what's going on. Apparently, at some point some HP-UX system
failed to completely support interface scanning under IPv6. The
symptom was that a a SIOCGLIFCONF ioctl might return an error with an
ENOENT value, in which case all you can do is log an error and return
This might have been fixed on HP-UX since the code was last touched;
in that case the code will never fire. On non-HP-UX systems it will
never fire anyway. On HP-UX systems that still have the bug, I think
removing this span will only have the effect that the ISC library
falls through to the handling for any non-EINVAL error and returns
ISC_R_UNEXPECTED rather than ISC_R_FAILURE
So unless Gary has spotted something I haven't, this code can be dropped.
I'd probably have removed it already if it weren't hiding in a pretty
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
Please consider contributing to my Patreon page at https://www.patreon.com/esr
so I can keep the invisible wheels of the Internet turning. Give generously -
the civilization you save might be your own.
More information about the devel