Date: Thu, 30 Apr 2009 16:36:38 +1000 (EST) From: Bruce Evans <brde@optusnet.com.au> To: Warner Losh <imp@FreeBSD.org> Cc: svn-src-head@FreeBSD.org, svn-src-all@FreeBSD.org, src-committers@FreeBSD.org Subject: Re: svn commit: r191677 - head/usr.bin/du Message-ID: <20090430162311.T2904@delplex.bde.org> In-Reply-To: <200904300124.n3U1Or1w097927@svn.freebsd.org> References: <200904300124.n3U1Or1w097927@svn.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090430162311.T2904>