From owner-freebsd-hackers Mon May 7 9:51:36 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id EF36937B422 for ; Mon, 7 May 2001 09:51:31 -0700 (PDT) (envelope-from des@ofug.org) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id SAA52291; Mon, 7 May 2001 18:51:23 +0200 (CEST) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Sheldon Hearn Cc: hackers@FreeBSD.ORG Subject: Re: sysctl(8) and opaque MIB entries References: <98295.989251948@axl.fw.uunet.co.za> From: Dag-Erling Smorgrav Date: 07 May 2001 18:51:22 +0200 In-Reply-To: <98295.989251948@axl.fw.uunet.co.za> Message-ID: Lines: 11 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sheldon Hearn 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 - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message