After building & installing @r268208 (yesterday), "sysctl hw.ncpu" reports a number (e.g., "2" for my laptop). After building & installing @r268244 (today)... freebeast(9.3-P)[5] sysctl hw.ncpu | hd 00000000 68 77 2e 6e 63 70 75 3a 20 0a |hw.ncpu: .| 0000000a freebeast(9.3-P)[6] After reverting r268244, then "cd /usr/src/sbin/sysctl && make && make install": g1-252(9.3-P)[8] sysctl hw.ncpu | hd 00000000 68 77 2e 6e 63 70 75 3a 20 32 0a |hw.ncpu: 2.| 0000000b g1-252(9.3-P)[9] I note that I also track stable/10 and head (on different slices; daily) on the machine; haven't seen similar behavior in either environment. Note that it is not uncommon for certain ports builds to expect to get a number from "sysctl -n hw.ncpu", and when that doesn't happen, the ports builds tend to stop working. Peace, david -- David H. Wolfskill david at catwhisker.org Taliban: Evil cowards with guns afraid of truth from a 14-year old girl. See http://www.catwhisker.org/~david/publickey.gpg for my public key. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 949 bytes Desc: not available URL: <http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20140704/a8bf1182/attachment.sig>
Hans Petter Selasky
2014-Jul-04 17:19 UTC
r268244 (stable/9) seems to break "sysctl hw.ncpu"
On 07/04/14 14:39, David Wolfskill wrote:> After building & installing @r268208 (yesterday), "sysctl hw.ncpu" > reports a number (e.g., "2" for my laptop). > > After building & installing @r268244 (today)... > > freebeast(9.3-P)[5] sysctl hw.ncpu | hd > 00000000 68 77 2e 6e 63 70 75 3a 20 0a |hw.ncpu: .| > 0000000a > freebeast(9.3-P)[6] > > After reverting r268244, then "cd /usr/src/sbin/sysctl && make && make > install": > > g1-252(9.3-P)[8] sysctl hw.ncpu | hd > 00000000 68 77 2e 6e 63 70 75 3a 20 32 0a |hw.ncpu: > 2.| > 0000000b > g1-252(9.3-P)[9] > > > I note that I also track stable/10 and head (on different slices; > daily) on the machine; haven't seen similar behavior in either > environment. > > Note that it is not uncommon for certain ports builds to expect to get a > number from "sysctl -n hw.ncpu", and when that doesn't happen, the ports > builds tend to stop working.Hi, I cannot reproduce this. Using the same kernel and running sysctl from. My patch to 9-stable will not affect printing of integers. 9-stable and 10-stable and current "sysctl" code all gives the same result over here with 9-stable kernel: sysctl -n hw.ncpu | hd 00000000 32 0a |2.| sysctl hw.ncpu | hd 00000000 68 77 2e 6e 63 70 75 3a 20 32 0a |hw.ncpu: 2.| Can you tell me exactly what kernel version you are using, "uname -a" and which version of "sysctl" with which version of the kernel is failing, so that I can reproduce. Thank you! --HPS