On Wed, 2014-10-15 at 07:36 +0200, Joachim Backes wrote:
> Hi all F21 testers,
>
> after having updated to procps-ng-3.3.10-3.fc21.x86_64, the new top
> command has some changed default behaviour (red lines, process tree
> display),...
>
> Additionally, the top command shows weird memory usage va
On 10/15/14 17:56, Ed Greshko wrote:
> On 10/15/14 16:32, Joachim Backes wrote:
>> Maybe, the free memory part is marked by the red part of the bar, and
>> the orange part signals the used part of the memory?
> Actually, if you do "man top" it has all the information. Just don't
> have time t
On 10/15/14 16:32, Joachim Backes wrote:
> Maybe, the free memory part is marked by the red part of the bar, and
> the orange part signals the used part of the memory?
Actually, if you do "man top" it has all the information. Just don't have
time to read it at the moment.
--
If you can't l
On 10/15/2014 08:43 AM, Ed Greshko wrote:
> On 10/15/14 13:36, Joachim Backes wrote:
>> Hi all F21 testers,
>>
>> after having updated to procps-ng-3.3.10-3.fc21.x86_64, the new top
>> command has some changed default behaviour (red lines, process tree
>> display),...
>>
>> Additionally, the top co
On 10/15/14 13:36, Joachim Backes wrote:
> Hi all F21 testers,
>
> after having updated to procps-ng-3.3.10-3.fc21.x86_64, the new top
> command has some changed default behaviour (red lines, process tree
> display),...
>
> Additionally, the top command shows weird memory usage values: My box
> has
Hi all F21 testers,
after having updated to procps-ng-3.3.10-3.fc21.x86_64, the new top
command has some changed default behaviour (red lines, process tree
display),...
Additionally, the top command shows weird memory usage values: My box
has 8GB mem, and top says:
GiB Mem : 17.9/7.798
Or must
