Opened 10 years ago

Closed 8 years ago

Last modified 8 years ago

#4328 closed bug (fixed)

[bin:top] 5 seconds is too much before displaying

Reported by: diver Owned by: axeld
Priority: normal Milestone: R1
Component: Applications/Command Line Tools Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: yes Platform: All

Description

Currently one have to wait 5 seconds before top will display process list, this is too much when you just want to quickly look around. It is also is too limited in options, maybe there is a bsd version?

Attachments (1)

patch_top.diff (1.2 KB ) - added by stpere 8 years ago.

Download all attachments as: .zip

Change History (12)

comment:1 by korli, 10 years ago

ps might be the tool you want to use then. top needs a little time to be able to display valid stats.

comment:2 by jackburton, 10 years ago

The problem is that the default delay for top is 5 seconds. But that delay shouldn't be applied before showing the initial screen.

comment:3 by diver, 10 years ago

Thanks Jerome, ps will do for now. BTW (sorry for offtopic), could you please have a look at auich driver in wrt VirtualBox, pretty please? :-)

comment:4 by diver, 10 years ago

Version: R1/pre-alpha1R1/Development

comment:5 by diver, 9 years ago

Still here in hrev38300.

comment:6 by mmadia, 9 years ago

Edited comment as the issue was explained over IRC.

Last edited 9 years ago by mmadia (previous) (diff)

by stpere, 8 years ago

Attachment: patch_top.diff added

comment:7 by stpere, 8 years ago

Has a Patch: set

comment:8 by stpere, 8 years ago

Can't commit yet, but when in "infinite iterations" mode, the first iteration will be done in half a second, then the others will follow the requested delay.

comment:9 by bonefish, 8 years ago

Applied in hrev42969. Thanks a lot and sorry for the delay!

comment:10 by bonefish, 8 years ago

Resolution: fixed
Status: newclosed

comment:11 by stpere, 8 years ago

Oh.. I'm sorry. I should have committed this myself before.. it slipped out of my mind. Thanks!!

Note: See TracTickets for help on using tickets.