bin/177860: top(1) does not show time units when time > 999 days.

Dmitry Sivachenko mitya at yandex-team.ru
Sun Apr 14 17:20:01 UTC 2013


>Number:         177860
>Category:       bin
>Synopsis:       top(1) does not show time units when time > 999 days.
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Apr 14 17:20:00 UTC 2013
>Closed-Date:
>Last-Modified:
>Originator:     Dmitry Sivachenko
>Release:        FreeBSD 10.0-CURRENT amd64
>Organization:
>Environment:
System: FreeBSD dhcp175-40-red.yandex.net 10.0-CURRENT FreeBSD 10.0-CURRENT #2: Mon Mar 25 17:10:25 MSK 2013 mitya at dhcp175-40-red.yandex.net:/usr/obj/usr/src/sys/CAVIA amd64


	
>Description:
On modern multiprocessor systems it is easy for multithreaded process to consume 
more than 999 hours of execution time.  In that case, 'H' unit is not shown in top(1)
output.

Below is the example output:
  PID USERNAME      THR PRI NICE   SIZE    RES STATE   C   TIME   WCPU COMMAND
 8556 UUUUUUUUU      17 118   20 33938M 24342M CPU11  11 1270.4 1457.67% XXXX

This process has 16 threads and it is running for few days.
It's execution time is 1270.4*hours*, but that 'H' unit is not shown.


>How-To-Repeat:


>Fix:


If execution time is more than 999 hours, I suggest to drop fraction (".4" in my example)
and use freed space with unit specifier.

Or, as an alternative, introduce another time unit "d" for "days".
>Release-Note:
>Audit-Trail:
>Unformatted:


More information about the freebsd-bugs mailing list