Date: Mon, 29 Nov 1999 18:45:52 -0600 (CST) From: toasty@dragondata.com To: FreeBSD-gnats-submit@freebsd.org Subject: bin/15174: sysctl(8) gives bogus diagnostic Message-ID: <199911300045.SAA42740@shell3.dragondata.com>
next in thread | raw e-mail | index | archive | help
>Number: 15174 >Category: bin >Synopsis: sysctl(8) gives bogus diagnostic >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Nov 29 16:50:01 PST 1999 >Closed-Date: >Last-Modified: >Originator: Kevin Day >Release: FreeBSD 4.0-CURRENT i386 >Organization: DragonData Internet Services >Environment: Any FreeBSD system with sysctl(8) >Description: sysctl -da gives a rather confusing message: su-2.03# sysctl -d -a sysctl: sysctl name -1 1024 2: No such file or directory I assumed this would give me the descriptions of all sysctls, but apparently not. I'll come up with a patch myself if someone tells me if it's supposed to allow this, or if it should smack you for doing something that it won't do. Is sysctl broken in that it won't do this, or is it not supposed to and just not printing a sensible error? >How-To-Repeat: sysctl -d -a >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199911300045.SAA42740>