From owner-freebsd-current@FreeBSD.ORG Mon Aug 25 13:21:50 2014 Return-Path: Delivered-To: freebsd-current@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 342019D4 for ; Mon, 25 Aug 2014 13:21:50 +0000 (UTC) Received: from smtp.vangyzen.net (hotblack.vangyzen.net [IPv6:2607:fc50:1000:7400:216:3eff:fe72:314f]) by mx1.freebsd.org (Postfix) with ESMTP id 1645B3AE3 for ; Mon, 25 Aug 2014 13:21:50 +0000 (UTC) Received: from marvin.lab.vangyzen.net (c-24-125-214-90.hsd1.va.comcast.net [24.125.214.90]) by smtp.vangyzen.net (Postfix) with ESMTPSA id 3094456436 for ; Mon, 25 Aug 2014 08:21:49 -0500 (CDT) Message-ID: <53FB386C.9030800@vangyzen.net> Date: Mon, 25 Aug 2014 09:21:48 -0400 From: Eric van Gyzen User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: ktrace -c behavior References: <53F79710.6090700@vangyzen.net> <20140822192034.GA71691@funkthat.com> <53F79971.4050802@vangyzen.net> <20140824235336.GR71691@funkthat.com> In-Reply-To: <20140824235336.GR71691@funkthat.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Aug 2014 13:21:50 -0000 On 08/24/2014 19:53, John-Mark Gurney wrote: > Eric van Gyzen wrote this message on Fri, Aug 22, 2014 at 15:26 -0400: >> On 08/22/2014 15:20, John-Mark Gurney wrote: >>> Eric van Gyzen wrote this message on Fri, Aug 22, 2014 at 15:16 -0400: >>>> What behavior would you expect from this sequence of commands? >>>> >>>> ktrace -tw -p 1234 >>>> ktrace -c -p 1234 >>>> >>>> Based on this... >>>> >>>> -c Clear the trace points associated with the specified file >>>> or processes. >>> and/or just add specified: >>> Clear the specified trace points ... >> But what if I didn't specify them? > You specified the default by not specificly specifing any different > ones.. :) Confused? :) Amused. :) > or maybe selected? Perhaps, but I didn't select them, either. My original suggestion is more--dare I use this word again--specific. It explains exactly how the command behaves. Eric