From owner-svn-src-all@FreeBSD.ORG Thu Apr 30 06:36:44 2009 Return-Path: Delivered-To: svn-src-all@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5C4A410656BD; Thu, 30 Apr 2009 06:36:44 +0000 (UTC) (envelope-from brde@optusnet.com.au) Received: from mail08.syd.optusnet.com.au (mail08.syd.optusnet.com.au [211.29.132.189]) by mx1.freebsd.org (Postfix) with ESMTP id CF7E48FC1A; Thu, 30 Apr 2009 06:36:43 +0000 (UTC) (envelope-from brde@optusnet.com.au) Received: from c122-107-120-227.carlnfd1.nsw.optusnet.com.au (c122-107-120-227.carlnfd1.nsw.optusnet.com.au [122.107.120.227]) by mail08.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id n3U6acfe021164 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 30 Apr 2009 16:36:39 +1000 Date: Thu, 30 Apr 2009 16:36:38 +1000 (EST) From: Bruce Evans X-X-Sender: bde@delplex.bde.org To: Warner Losh In-Reply-To: <200904300124.n3U1Or1w097927@svn.freebsd.org> Message-ID: <20090430162311.T2904@delplex.bde.org> References: <200904300124.n3U1Or1w097927@svn.freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: svn-src-head@FreeBSD.org, svn-src-all@FreeBSD.org, src-committers@FreeBSD.org Subject: Re: svn commit: r191677 - head/usr.bin/du X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Apr 2009 06:36:45 -0000 On Thu, 30 Apr 2009, Warner Losh wrote: > Log: > Report the next directory being scanned when a ^T is pressed (or any > SIGINFO). Provides some progress report for the impatient. The impatient should use a tracing utility instead of encrufting individual utilities. > This > won't report that we're blocking in our walk due to disk/network > problems, however. There's no really good way to report that > condition that I'm aware of... Tracing utilities coulld be extended to report kernel info. E.g., the current [blocked] syscall can be found and reported in the same way and detail that ddb does for backtrace and ps. Names would be harder to find, but a full backtrace normally locates what is blocking. Bruce