Sheldon Hearn <[EMAIL PROTECTED]> writes: > Is there a good reason why sysctl(8) won't display _any_ output for > opaque MIB entries named as arguments? Yes it will, with -X. The interesting question is why there isn't an option to make it display just one variable in hex, and why it doesn't print a message when it omits printing an opaque variable. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
- sysctl(8) and opaque MIB entries Sheldon Hearn
- Re: sysctl(8) and opaque MIB entries Dag-Erling Smorgrav
- Re: sysctl(8) and opaque MIB entries Sheldon Hearn
- Re: sysctl(8) and opaque MIB entries Dag-Erling Smorgrav
- Re: sysctl(8) and opaque MIB entries Peter Pentchev
- Re: sysctl(8) and opaque MIB ent... Dag-Erling Smorgrav
- Re: sysctl(8) and opaque MIB... Peter Pentchev
- Re: sysctl(8) and opaque... Dag-Erling Smorgrav
- Re: sysctl(8) and opaque MIB entries Poul-Henning Kamp
- Re: sysctl(8) and opaque MIB entries Peter Pentchev
- Re: sysctl(8) and opaque MIB entries Dag-Erling Smorgrav
- Re: sysctl(8) and opaque MIB entries Sheldon Hearn