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 _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
