>Number:         3195
>Category:       misc
>Synopsis:       missing 'k' in ktrace.1
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    misc-bug-people (Misc Bug People)
>State:          open
>Class:          doc-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Feb  6 00:35:00 1997
>Last-Modified:
>Originator:     SAITOH Masanobu
>Organization:
>Release:        latest -current
>Environment:
System: NetBSD ifree.spa.is.uec.ac.jp 1.2B NetBSD 1.2B (IFREE) #29: Wed Jan 15 15:58:05 JST 1997 msaitoh@ifree.spa.is.uec.ac.jp:/var/sources/src/sys/arch/i386/compile/IFREE i386


>Description:
	Try 'man ktrace'

 >   Once tracing is enabled on a process, trace data will be logged until ei-
 >   ther the process exits or the trace point is cleared.  A traced process
 >   can generate enormous amounts of log data quickly; It is strongly sug-
 >   gested that users memorize how to disable tracing before attempting to
 >   trace a process.  The following command is sufficient to disable tracing
 >   on all user owned processes, and, if executed by root, all processes:
 > 
 >         $ trace -C
	    **

	'k' is missing.

>How-To-Repeat:
	man ktrace
>Fix:
	Apply following patch:
--- ktrace.1.orig	Fri Jan 10 21:24:23 1997
+++ ktrace.1	Thu Feb  6 17:18:18 1997
@@ -69,7 +69,7 @@
 The following command is sufficient to disable tracing on all user owned
 processes, and, if executed by root, all processes:
 .Pp
-.Dl \&$ trace -C
+.Dl \&$ ktrace -C
 .Pp
 The trace file is not human readable; use
 .Xr kdump 1

>Audit-Trail:
>Unformatted: