Date: Mon, 29 Jun 2015 19:57:41 -0400 From: Patrick Kelsey <pkelsey@freebsd.org> To: Hans Petter Selasky <hps@selasky.org> Cc: Sean Bruno <sbruno@freebsd.org>, "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org> Subject: Re: sysctl(3) man page examples Message-ID: <CAD44qMWN_sQXzKc7uN70jiKTG_XumTgWga5%2BqX3jQyTZZjG=2w@mail.gmail.com> In-Reply-To: <5591906E.8060904@selasky.org> References: <558F1D88.8010407@ignoranthack.me> <CAD44qMUVPH4eY4zBfkBQ_m0Vhxg0M1CM7TXZv9emKjWdV8jTVg@mail.gmail.com> <5591906E.8060904@selasky.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jun 29, 2015 at 2:37 PM, Hans Petter Selasky <hps@selasky.org> wrote: > On 06/28/15 08:26, Patrick Kelsey wrote: > >> s a sysctl entry for it (containing an empty >> string) >> > > Hi, > > FYI: > > Until r267960 zero-length strings were not listed by sysctl, which might > be part of the reason this bug has not been seen before. > > That zero-length string is just a dummy entry to keep the mib name in the sysctl tree - the true value for that key is supplied by sysctl(3) directly, so that key should never validly resolve to a zero-length string. I believe this bug did not show up because there are vanishingly few consumers of the user.cs_path sysctl value. -Patrick
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAD44qMWN_sQXzKc7uN70jiKTG_XumTgWga5%2BqX3jQyTZZjG=2w>