On Wed, 19 Nov 2014 14:51:11 +0100 Karol Blazewicz <karol.blazewicz@xxxxxxxxx> wrote: > On Wed, Nov 19, 2014 at 2:39 PM, Ralf Mardorf > <ralf.mardorf@xxxxxxxxxxxxxx> wrote: > > I installed procps-ng-classic, but this alone didn't bring back the > > old useful top, I needed to remove ~/.toprc too and now the > > resource hungriest process is shown again. > > > > What exactly is the new style good for, if it can happen, that the > > resource hungriest process isn't listed, while absolutely irrelevant > > processes are listed? > > > > IMO Arch Linux shouldn't follow upstream, if upstream decide to do > > something that idiotic for a much used command line tool. > > I followed procps-ng-sucks suggestions and my procps-ng top works for > me - shows the resource hogs just fine. You can use htop if you want. I'm aware about htop and atop, I used them sometimes in the past, but top is a basic tool and shouldn't be changed in such an absurd way.
