Description of problem: With last update procps-ng output of top program is terrible. It has RED color and tree view. It is not good for eye and psychology and not allow quickly see most heavy load programs. Version-Release number of selected component (if applicable): procps-ng-3.3.10-3.fc21 How reproducible: Always Steps to Reproduce: 1. Just run top Additional info: Please return at least old output mode of top.
And also need return type of loading like %sys %idle %wa etc.
Hello Vasiliy. It seems you haven't tried to explore the new top yet. You can do that by yourself by pressing the following combination of keys (respect the capital letters and note, that the character next to 'z' is digit '1', not letter 'l'): tttmmVbz1W The above disables the cpu/memory graph modes, disables the forest view, changes reversed to bold, turns the colors off, disables the per-cpu stats and writes the configuration down. But ... even when you consider the new top look hostile, I know it is just about how your brain accepts/rejects the unexpected layout change and surprise that breaks your habbits. The same happened in my case when I saw that for the first time, but I decided to give it a try and got used to it quite quickly. Well, to be honest I did few tweaks by switching the forrest view off, changing reversed to bold, changing the cpu graph mode from lines to filled bars and saving the config (key combination "VbtW" after removing ~/.toprc). If you don't like the red and brown color, you can define your own colors with the 'Z' key, but honestly, I haven't found a better looking color combination than the default one. Please, let me know whether you're ok with the hints above. Thanks, Jaromir.
... maybe one more hint ... you can change the set of columns and their order and sort order by pressing the 'f' key and then following the instructions in the header.
I am understand that I can do it via keys and save to .toprc. But if a new view good for all users by default? Many users will be forced to do this manipulations. Whatever it was we can return to discussion after Fedora 21 Release and more people update their systems.
Hello Vasiliy. We'll probably newer get enough feedback to get accurate stats. You would have to let people vote. By changing the defaults the 'top' tells users that the new features exist, as majority of users is not aware of any enhancements made in the tool during the last few years. I was thinking about that a lot and this way we can achieve an enlightenment and that's intended. Regards, Jaromir.
@Jaromír I think we should use the old style as default. The new look is really terrible and many users do not know how to get the old style. Please check: https://mstevens.fedorapeople.org/img/top.png and https://admin.fedoraproject.org/updates/FEDORA-2014-12798/open-vm-tools-9.4.6-4.fc21,procps-ng-3.3.10-3.fc21
Hi, guys! I agree with Vasiliy Glazov that new style of top is not very well.
I agree with Vasiliy Glazov that new style of top is not good.
I think this new top is a nice improvement in general. Maybe the default colors could be a bit softer on the eye though ;) Maybe start off with normal white/gray for the process tree and the same colors for cpu? Or maybe user the terminal colors-d facility from util-linux? (haven't checked if it's already used and the defaults there need revisiting) http://karelzak.blogspot.it/2014/04/terminal-colorsd.html
(In reply to Jaromír Cápík from comment #2) > tttmmVbz1W Thank you. I will be able to use this as a starting point for my own configuration. Is there a way to configure a target to be printed using the default foreground color, so that it's white if the terminal has black background and vice-versa?
Created attachment 947745 [details] top in GNOME This looks even more terible with GNOME's default color scheme. The red looks barely readable. Could we turn on the monochromatic scheme back? It makes no assumption about terminal background. Given we basically only use two colors (red & brown) this should not be a big issue.
Also, seems like the top can't be configured sanely system-wide. /etc/toprc looks rather useless for this purpose :(
I'm discussing all your comments with the author. But now I'm more interested in the overflow seen on the picture. Lubomire, could you please reproduce the overflow issue on the Mem line and then switch the memory graphs back to the old mode by pressing the 'm' key twice? I'd like to know all the numbers on the Mem and the Swap line. Thanks, Jaromir.
(In reply to Morten Stevens from comment #6) > @Jaromír > > I think we should use the old style as default. > > The new look is really terrible and many users do not know how to get the > old style. This goes against the idea of teaching people. I wanted to show people how to tweak the settings. If the users don't know, then they should learn how instead of consuming what's served. Anyway, I'm sick of fighting with people who are able to give negative karma just because of their inability to accept changes in the look. It is not a valid reason for negative karma.
I just disabled the new defaults.
(In reply to Jaromír Cápík from comment #14) > [people] give negative karma just because of their inability to accept > changes in the look. It is not a valid reason for negative karma. Well, I did not give negative karma, but I can understand why people would think at least some of the changes were bugs. I myself did suspect at first that the dominantly red look was a bug, until I found this BZ. It really was hardly readable on my dark terminal. The update description contained the sentence "top offers new startup defaults" among the 20 (or so) lines, but in my view this did not sufficiently highlight the nature and intention of these changes. As for the individual changes themselves, in my view: I do not understand how the process tree view can be useful. I makes the CPU-hungry processes that I mainly want to see when I run top not appear on the screen at all. I dislike the red color by default. I really like the bar graphs for per-CPU loads. They instantly communicate to me the idea of the CPU load (though I acknowledge bug 1153820).
Created attachment 948638 [details] red on black Red on black looks well in my case ... I think it's only about habits. Like I stated above, at first I didn't like the colours, but after few weeks everything changed and now I don't like the old defaults.
procps-ng-3.3.10-4.fc21,open-vm-tools-9.4.6-4.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/procps-ng-3.3.10-4.fc21,open-vm-tools-9.4.6-4.fc21
(In reply to Jaromír Cápík from comment #14) > This goes against the idea of teaching people. I wanted to show people how > to tweak the settings. If the users don't know, then they should learn how > instead of consuming what's served. > Anyway, I'm sick of fighting with people who are able to give negative karma > just because of their inability to accept changes in the look. It is not a > valid reason for negative karma. The reason for my negative karma was: The new startup defaults were unusable for me. The "top" command is an integral part of every UNIX system and the new startup default doesn't work as expected for me and many other users. The other reason was: We've still another process monitoring software with colors: htop Nevertheless, thank you for going back to the old defaults.
(In reply to Morten Stevens from comment #19) > The reason for my negative karma was: The new startup defaults were unusable > for me. The "top" command is an integral part of every UNIX system Sorry to disagree here. The 'top' tool is not available on all UNIX systems. > and the > new startup default doesn't work as expected for me and many other users. Well, many = 5 in our case. But we also had 2 users, who liked the new changes. But it's common that satisfied people don't say a word and those who disagree can kill the whole idea and a lot of effort in few seconds. And with no comments or comments like "the new top behaviour is odd". The only valid negative karma I accept was that from Lubomir Rintel, who filled useful comments and also submitted bug reports. > The other reason was: We've still another process monitoring software with > colors: htop Yes, and you're the co-maintainer. I know. That's why I thought you take that as a competition. > Nevertheless, thank you for going back to the old defaults. I had no choice. It's like hitting the wall with head. I wanted to bring all the 3.3.10 enhancements to users as soon as possible and to bump the API prior beta freeze and spent a lot of time on this task. You have no idea, how frustrating this is.
3.3.8-17 vs. 3.3.10-4, tested on Fedora 20. "free" and "used" columns did swap the order.
Created attachment 948746 [details] 3.3.8-17 - old
Created attachment 948747 [details] 3.3.10-4 - new
(In reply to Jaromír Cápík from comment #20) > Yes, and you're the co-maintainer. I know. That's why I thought you take > that as a competition. To make this clear: No, this was not a competition for me. Yes, I'm co-maintainer for htop, but this has no impact on my karma rating. Personally, I prefer top instead of htop.
(In reply to Jaromír Cápík from comment #13) > I'm discussing all your comments with the author. > > But now I'm more interested in the overflow seen on the picture. > Lubomire, could you please reproduce the overflow issue on the > Mem line and then switch the memory graphs back to the old mode > by pressing the 'm' key twice? > I'd like to know all the numbers on the Mem and the Swap line. > > Thanks, > Jaromir. I also has wrong data for mem in bar view. In number mode: GiB Mem : 5,829 total, 0,584 free, 2,791 used, 2,454 buff/cache GiB Swap: 2,000 total, 1,994 free, 0,006 used. 2,647 avail Mem In bar mode: GiB Mem : 54,2/5,829 [||||||||||||||||||||||||||||||||||||||||||||||||||||||| ] GiB Swap: 0,3/2,000 [ ] It is for procps-ng-3.3.10-3.fc21.x86_64
(In reply to Xose Vazquez Perez from comment #21) > 3.3.8-17 vs. 3.3.10-4, tested on Fedora 20. > > "free" and "used" columns did swap the order. Hi Xose. Yes, that's true. Moreover the cached is now joined with buffers and a new entry called "avail Mem" appeared under.
> I also has wrong data for mem in bar view. > In number mode: > GiB Mem : 5,829 total, 0,584 free, 2,791 used, 2,454 buff/cache > GiB Swap: 2,000 total, 1,994 free, 0,006 used. 2,647 avail Mem > > In bar mode: > GiB Mem : 54,2/5,829 > [||||||||||||||||||||||||||||||||||||||||||||||||||||||| > ] > GiB Swap: 0,3/2,000 [ > ] > > It is for procps-ng-3.3.10-3.fc21.x86_64 Nope, it's correct in your case. The number represents a percentage of available/unavailable memory. Nowadays the value reported as 'free' loses the importance as a lot of memory is usually ocuppied by caches, but usually a lot of that space can be reclaimed. Moreover, a part of the space reported as free is protected by the kernel and cannot be used. That's why you should look at the 'avail Mem' field instead of the 'free' field. The latest procps-ng reflects the latest changes in the kernel memory management and I expect questions and confusions till users get used to that.
Package procps-ng-3.3.10-4.fc21, open-vm-tools-9.4.6-4.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing procps-ng-3.3.10-4.fc21 open-vm-tools-9.4.6-4.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-13392/procps-ng-3.3.10-4.fc21,open-vm-tools-9.4.6-4.fc21 then log in and leave karma (feedback).
procps-ng-3.3.10-4.fc21, open-vm-tools-9.4.6-4.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.