top: tweaked the recently introduced 'STARTED' support
When the 'STARTED' field was added, the width was made
the same as the 'TIME+' field. Thus, a full time could
be shown (which then included hundredths of a second).
That kind of granularity is totally unnecessary. After
all, this column is potentially confusing enough since
it is so counterintuitive. So, this commit will reduce
the width of the field with some help from scale_tics.
Henceforth it will not include those ol' centiseconds.
[ along the way let's expand the man document with a ]
[ a remainder about content representation & scaling ]
Reference(s):
. introduced 'start time' field
commit 7647e96b0a
Signed-off-by: Jim Warner <james.warner@comcast.net>
This commit is contained in:
@@ -980,10 +980,15 @@ member of the session, called the session leader, which is usually the
|
||||
login shell.
|
||||
|
||||
.TP 4
|
||||
\fBSTARTED \*(Em Start Time \fR
|
||||
\fBSTARTED \*(Em Start Time Interval\fR
|
||||
The length of time since system boot when a process started.
|
||||
Thus, the most recently started task will display the largest time interval.
|
||||
|
||||
The value will be expressed as 'MM:SS' (minutes:sceonds) until the
|
||||
interval becomes too great to fit column width.
|
||||
At that point it will be scaled to 'HH,MM' (hours,minutes) and possibly
|
||||
beyond.
|
||||
|
||||
.TP 4
|
||||
\fBSUID \*(Em Saved User Id \fR
|
||||
The\fI saved\fR user ID.
|
||||
|
Reference in New Issue
Block a user