hi there,
any reason why bin/139389 hasn't been committed, yet? i think seeing the thread
id in top -H output is extremely useful!
cheers.
alex
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To
On 6 July 2011 13:19, Alexander Best arun...@freebsd.org wrote:
hi there,
any reason why bin/139389 hasn't been committed, yet? i think seeing the
thread
id in top -H output is extremely useful!
I think the main reason is that tid takes a log of space (6 digits + 2 spaces),
and top already
On Wed Jul 6 11, Sergey Kandaurov wrote:
On 6 July 2011 13:19, Alexander Best arun...@freebsd.org wrote:
hi there,
any reason why bin/139389 hasn't been committed, yet? i think seeing the
thread
id in top -H output is extremely useful!
I think the main reason is that tid takes a
On Wed Jul 6 11, Alexander Best wrote:
On Wed Jul 6 11, Sergey Kandaurov wrote:
On 6 July 2011 13:19, Alexander Best arun...@freebsd.org wrote:
hi there,
any reason why bin/139389 hasn't been committed, yet? i think seeing the
thread
id in top -H output is extremely useful!
