Skip to content
Branch: master
Go to file
Code

Latest commit

Atoptool committed ef62300 Jun 15, 2020
Occasional segmentation fault when atop is combined with netatop
Even when the number of exited processes via netatop was zero, still
a malloc was issued. In certain circumstances a structure could have
been stored at the address that was returned by malloc, resulting in
a segmentation fault on a subsequent malloc.

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
man
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

README.md

atop

Created/maintained by Gerlof Langeveld gerlof.langeveld@atoptool.nl

Introduction

Atop is an ASCII full-screen performance monitor for Linux that is capable of reporting the activity of all processes (even if processes have finished during the interval), daily logging of system and process activity for long-term analysis, highlighting overloaded system resources by using colors, etcetera. At regular intervals, it shows system-level activity related to the CPU, memory, swap, disks (including LVM) and network layers, and for every process (and thread) it shows e.g. the CPU utilization, memory growth, disk utilization, priority, username, state, and exit code. In combination with the optional kernel module netatop, it even shows network activity per process/thread. In combination with the optional daemon atopgpud, it also shows GPU activity on system level and process level.

Highlights

The command atop has some major advantages compared to other performance monitoring tools:

  • Resource consumption by all processes. It shows the resource consumption by all processes that were active during the interval, so also the resource consumption by those processes that have finished during the interval.

  • Utilization of all relevant resources. Obviously it shows system-level counters concerning utilization of cpu and memory/swap, however it also shows disk I/O and network utilization counters on system level.

  • Permanent logging of resource utilization. It is able to store raw counters in a file for long-term analysis on system level and process level. These raw counters are compressed at the moment of writing to minimize disk space usage. By default, the daily logfiles are preserved for 28 days. System activity reports can be generated from a logfile by using the atopsar command.

  • Highlight critical resources. It highlights resources that have (almost) reached a critical load by using colors for the system statistics.

  • Scalable window width. It is able to add or remove columns dynamically at the moment that you enlarge or shrink the width of your window.

  • Resource consumption by individual threads. It is able to show the resource consumption for each thread within a process.

  • Watch activity only. By default, it only shows system resources and processes that were really active during the last interval, so output related to resources or processes that were completely passive during the interval is by default suppressed.

  • Watch deviations only. For the active system resources and processes, only the load during the last interval is shown (not the accumulated utilization since system boot or process startup).

  • Accumulated process activity per user. For each interval, it is able to accumulate the resource consumption for all processes per user.

  • Accumulated process activity per program. For each interval, it is able to accumulate the resource consumption for all processes with the same name.

  • Accumulated process activity per container. For each interval, it is able to accumulate the resource consumption for all processes within the same container.

  • Network activity per process. In combination with the optional kernel module netatop, it shows process-level counters concerning the number of TCP and UDP packets transferred, and the consumed network bandwidth per process.

  • GPU activity on system level and per process. In combination with the optional daemon atopgpud, it shows system-level and process-level counters concerning the load and memory utilization per GPU.

You can’t perform that action at this time.