Date: Thu, 26 Jul 2018 22:08:15 -0700 From: Conrad Meyer <cem@freebsd.org> To: Shane Ambler <FreeBSD@shaneware.biz> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: Changes to sysctl values Message-ID: <CAG6CVpXoa-f7Mp7_T4SOyC1wBKNuBv1EzjWkS5%2BzbgR_1pHvyA@mail.gmail.com> In-Reply-To: <e8498497-00df-81d8-3bf8-4d4179113532@ShaneWare.Biz> References: <e8498497-00df-81d8-3bf8-4d4179113532@ShaneWare.Biz>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jul 26, 2018 at 8:52 PM, Shane Ambler <FreeBSD@shaneware.biz> wrote: > I use devel/py-sysctl in some scripts to get values, using a recent > 12-current (r336728) I see at least two values that get a different > value type than on 11-stable. Same version of python and port. > ... Hi Shane, At some point, new sysctl types were added to the kernel, including CTLTYPE_U32. As part of the conversion to the counter(9) API, it seems the v_wire_count (and other vm.stats sysctls) changed to U32 type. py-sysctl lacks support for CTLTYPE_U32 and defaults to giving you a bytearray for unrecognized types. Best, Conrad
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAG6CVpXoa-f7Mp7_T4SOyC1wBKNuBv1EzjWkS5%2BzbgR_1pHvyA>