From owner-svn-src-head@FreeBSD.ORG Tue Sep 9 14:31:57 2014 Return-Path: Delivered-To: svn-src-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D8F7DAF8; Tue, 9 Sep 2014 14:31:56 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C344A262; Tue, 9 Sep 2014 14:31:56 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id s89EVuh4096213; Tue, 9 Sep 2014 14:31:56 GMT (envelope-from joel@FreeBSD.org) Received: (from joel@localhost) by svn.freebsd.org (8.14.9/8.14.9/Submit) id s89EVu8h096212; Tue, 9 Sep 2014 14:31:56 GMT (envelope-from joel@FreeBSD.org) Message-Id: <201409091431.s89EVu8h096212@svn.freebsd.org> X-Authentication-Warning: svn.freebsd.org: joel set sender to joel@FreeBSD.org using -f From: Joel Dahl Date: Tue, 9 Sep 2014 14:31:56 +0000 (UTC) To: src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: svn commit: r271314 - head/share/man/man9 X-SVN-Group: head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-src-head@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: SVN commit messages for the src tree for head/-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Sep 2014 14:31:57 -0000 Author: joel (doc committer) Date: Tue Sep 9 14:31:56 2014 New Revision: 271314 URL: http://svnweb.freebsd.org/changeset/base/271314 Log: - Add missing " - Sort sections Modified: head/share/man/man9/sysctl.9 Modified: head/share/man/man9/sysctl.9 ============================================================================== --- head/share/man/man9/sysctl.9 Tue Sep 9 14:20:55 2014 (r271313) +++ head/share/man/man9/sysctl.9 Tue Sep 9 14:31:56 2014 (r271314) @@ -105,7 +105,7 @@ .Fa "void *ptr" .Fa "intptr_t len" .Fa "const char *format" -.Fa "const char *descr +.Fa "const char *descr" .Fc .Ft struct sysctl_oid * .Fo SYSCTL_ADD_PROC @@ -505,49 +505,6 @@ enviroment early during module load or s .It Dv CTLFLAG_DYN Dynamically created OIDs automatically get this flag set. .El -.Sh SECURITY CONSIDERATIONS -When creating new sysctls, careful attention should be paid to the security -implications of the monitoring or management interface being created. -Most sysctls present in the kernel are read-only or writable only by the -superuser. -Sysctls exporting extensive information on system data structures and -operation, especially those implemented using procedures, will wish to -implement access control to limit the undesired exposure of information about -other processes, network connections, etc. -.Pp -The following top level sysctl name spaces are commonly used: -.Bl -tag -width ".Va regression" -.It Va compat -Compatibility layer information. -.It Va debug -Debugging information. -Various name spaces exist under -.Va debug . -.It Va hw -Hardware and device driver information. -.It Va kern -Kernel behavior tuning; generally deprecated in favor of more specific -name spaces. -.It Va machdep -Machine-dependent configuration parameters. -.It Va net -Network subsystem. -Various protocols have name spaces under -.Va net . -.It Va regression -Regression test configuration and information. -.It Va security -Security and security-policy configuration and information. -.It Va sysctl -Reserved name space for the implementation of sysctl. -.It Va user -Configuration settings relating to user application behavior. -Generally, configuring applications using kernel sysctls is discouraged. -.It Va vfs -Virtual file system configuration and information. -.It Va vm -Virtual memory subsystem configuration and information. -.El .Sh EXAMPLES Sample use of .Fn SYSCTL_DECL @@ -702,3 +659,46 @@ addition of MIB nodes. .Pp This man page was written by .An Robert N. M. Watson . +.Sh SECURITY CONSIDERATIONS +When creating new sysctls, careful attention should be paid to the security +implications of the monitoring or management interface being created. +Most sysctls present in the kernel are read-only or writable only by the +superuser. +Sysctls exporting extensive information on system data structures and +operation, especially those implemented using procedures, will wish to +implement access control to limit the undesired exposure of information about +other processes, network connections, etc. +.Pp +The following top level sysctl name spaces are commonly used: +.Bl -tag -width ".Va regression" +.It Va compat +Compatibility layer information. +.It Va debug +Debugging information. +Various name spaces exist under +.Va debug . +.It Va hw +Hardware and device driver information. +.It Va kern +Kernel behavior tuning; generally deprecated in favor of more specific +name spaces. +.It Va machdep +Machine-dependent configuration parameters. +.It Va net +Network subsystem. +Various protocols have name spaces under +.Va net . +.It Va regression +Regression test configuration and information. +.It Va security +Security and security-policy configuration and information. +.It Va sysctl +Reserved name space for the implementation of sysctl. +.It Va user +Configuration settings relating to user application behavior. +Generally, configuring applications using kernel sysctls is discouraged. +.It Va vfs +Virtual file system configuration and information. +.It Va vm +Virtual memory subsystem configuration and information. +.El