Skip site navigation (1)Skip section navigation (2)

Site Navigation

PRs for manpage 'top(1)'

This is an experimental report containing PRs for manpage 'top(1)' as of Fri May 30 07:39:49 2014 UTC. See notes.

PRs for manpage 'top(1)':
o2013/10/20bin/183135top(1) doesn't show results of swapon while running, only swapoff
o2013/09/18bin/182204top(1) is using wrong word when viewing threads
o2013/07/31bin/180961[patch] top(1): Fix top command format when JID with 4 characters is displayed
o2013/04/14bin/177860top(1) does not show time units when time > 999 days.
o2012/11/28bin/173973rpaulo[patch] 'not function' for user display for top(1)
o2010/01/17docs/142917arundel[patch] top(1) man page does not include information about VCSW and IVCSW
o2009/10/07bin/139389[patch] Change top(1) to display thread IDs
o2009/01/11docs/130364arundelMan page for top(1) needs explanation of CPU states
o2009/01/10bin/130343top(1): kvm_open: cannot open /proc/42997/mem corrupts screen output
o2008/10/17kern/128177jeff[sched_ule] wrong CPU usage reported by top(1)/ps(1) with SCHED_ULE
o2008/09/25bin/127633edwin[patch] Update top(1) to 3.8b1
o2007/11/29docs/118332arundelman page for top(1) does not describe STATE column wait events
o2006/11/26bin/105860top(1) user ID misalignment in mixer username/uid mode
o2006/09/02bin/102793edwin[patch] [request] top(1): display feature of current CPU frequency
o2005/11/30bin/89762edwin[patch] top(1) startup is very slow on system with many users
o2004/10/30kern/73328edwin[patch] top(1) shows NICE as -111 on processes started by idprio
o2004/02/28bin/63489top(1) finger(1) segfault when using NIS groups to restrict logins
o2002/12/04bin/45990top(1) dumps core if specific errors in password file
o2002/07/31bin/41213top(1) blocks if NIS-related entries in passwd(5) are in a certain order
19 problems total.


GNATS has no finer-grained categorization than 'kern', 'bin', 'ports', and so forth. To augment this, the bugmeisters have adopted the convention of adding '<name>(<section>)' to the Synopsis field. Consider this a prototype of a better search function.

Please give feedback on this report to Thanks.

Bugs can be in one of several states:

o - open
A problem report has been submitted, no sanity checking performed.
a - analyzed
The problem is understood and a solution is being sought.
f - feedback
Further work requires additional information from the originator or the community - possibly confirmation of the effectiveness of a proposed solution.
p - patched
A patch has been committed, but some issues (MFC and / or confirmation from originator) are still open.
r - repocopy
The resolution of the problem report is dependent on a repocopy operation within the CVS repository which is awaiting completion.
s - suspended
The problem is not being worked on, due to lack of information or resources. This is a prime candidate for somebody who is looking for a project to do. If the problem cannot be solved at all, it will be closed, rather than suspended.
c - closed
A problem report is closed when any changes have been integrated, documented, and tested -- or when fixing the problem is abandoned.