1ATOPSAR(1) General Commands Manual ATOPSAR(1)
2
6 atopsar - AT Computing's System Activity Report (atop related)
7
9 atopsar [-flags...] [-r file|date ] [-R cnt ] [-b hh:mm ] [-e hh:mm ]
10 atopsar [-flags...] interval [ samples ]
11
13 The program atopsar can be used to report statistics on system level.
14 In the first synopsis line (no sampling interval specified), atopsar
16 extracts data from a raw logfile that has been recorded previously by
17 the program atop (option -w of the atop program).
18 You can specify the name of the logfile with the -r option of the atop‐
19 sar program. When a daily logfile of atop is used, named
20 /var/log/atop/atop_YYYYMMDD (where YYYYMMDD reflects the date), the
21 required date of the form YYYYMMDD can be specified with the -r option
22 instead of the filename, or the symbolic name 'y' can be used for yes‐
23 terday's daily logfile (this can be repeated so 'yyyy' indicates the
24 logfile of four days ago). If the -r option is not specified at all,
25 today's daily logfile is used by default.
26 The starting and ending times of the report can be defined using the
27 options -b and -e followed by a time argument of the form hh:mm.
28 In the second synopsis line, atopsar reads actual activity counters
30 from the kernel with the specified interval (in seconds) and the speci‐
31 fied number of samples (optionally). When atopsar is activated in this
32 way it immediately sends the output for every requested report to stan‐
33 dard output. If only one type of report is requested, the header is
34 printed once and after every interval seconds the statistical counters
35 are shown for that period. If several reports are requested, a header
36 is printed per sample followed by the statistical counters for that
37 period.
38 Some generic flags can be specified to influence the behaviour of the
40 atopsar program:
41 -S By default the timestamp at the beginning of a line is suppressed
43 if more lines are shown for one interval. With this flag a time‐
44 stamp is given for every output-line (easier for post-processing).
45 -a By default certain resources as disks and network interfaces are
47 only shown when they were active during the interval. With this
48 flag all resources of a given type are shown, even if they were
49 inactive during the interval.
50 -x By default atopsar only uses colors if output is directed to a
52 terminal (window). These colors might indicate that a critical
53 occupation percentage has been reached (red) or has been almost
54 reached (cyan) for a particular resource. See the man-page of
55 atop for a detailed description of this feature (section COLORS).
56 With the flag -x the use of colors is suppressed unconditionally.
57 -C By default atopsar only uses colors if output is directed to a
59 terminal (window). These colors might indicate that a critical
60 occupation percentage has been reached (red) or has been almost
61 reached (cyan) for a particular resource. See the man-page of
62 atop for a detailed description of this feature (section COLORS).
63 With the flag -C colors will always be used, even if output is not
64 directed to a terminal.
65 -M Use markers at the end of a line to indicate that a critical occu‐
67 pation percentage has been reached ('*') or has been almost
68 reached ('+') for particular resources. The marker '*' is similar
69 to the color red and the marker '+' to the color cyan. See the
70 man-page of atop for a detailed description of these colors (sec‐
71 tion COLORS).
72 -H Repeat the header line within a report for every N detail lines.
74 The value of N is determined dynamically in case of output to a
75 tty/window (depending on the number of lines); for output to a
76 file or pipe this value is 23.
77 -R Summarize cnt samples into one sample. When the logfile contains
79 e.g. samples of 10 minutes, the use of the flag '-R 6' shows a
80 report with one sample for every hour.
81 Other flags are used to define which reports are required:
83 -A Show all possible reports.
85 -c Report about CPU utilization (in total and per cpu).
87 -p Report about processor-related matters, like load-averages and
89 hardware interrupts.
90 -P Report about processes.
92 -m Current memory- and swap-occupation.
94 -s Report about paging- and swapping-activity, and overcommitment.
96 -l Report about utilization of logical volumes.
98 -f Report about utilization of multiple devices.
100 -d Report about utilization of disks.
102 -i Report about the network interfaces.
104 -I Report about errors for network-interfaces.
106 -w Report about IP version 4 network traffic.
108 -W Report about errors for IP version 4 traffic.
110 -y General report about ICMP version 4 layer activity.
112 -Y Per-type report about ICMP version 4 layer activity.
114 -u Report about UDP version 4 network traffic.
116 -z Report about IP version 6 network traffic.
118 -Z Report about errors for IP version 6 traffic.
120 -k General report about ICMP version 6 layer activity.
122 -K Per-type report about ICMP version 6 layer activity.
124 -U Report about UDP version 6 network traffic.
126 -t Report about TCP network traffic.
128 -T Report about errors for TCP-traffic.
130 -O Report about top-3 processes consuming most processor capacity.
132 -G Report about top-3 processes consuming most resident memory.
134 -D Report about top-3 processes issueing most disk transfers.
136 -N Report about top-3 processes issueing most IPv4/IPv6 socket trans‐
138 fers.
139
141 Depending on the requested report, a number of columns with output val‐
142 ues are produced. The values are mostly presented as a number of
143 events per second.
144 The output for the flag -c contains the following columns per cpu:
146 usr% Percentage of cpu-time consumed in user mode (program text)
148 for all active processes running with a nice value of zero
149 (default) or a negative nice value (which means a higher
150 priority than usual). The cpu consumption in user mode of
151 processes with a nice value larger than zero (lower prior‐
152 ity) is indicated in the nice%-column.
153 nice% Percentage of cpu time consumed in user mode (i.e. program
155 text) for all processes running witn a nice value larger
156 than zero (which means with a lower priority than average).
157 sys% Percentage of cpu time consumed in system mode (kernel
159 text) for all active processes. A high percentage usually
160 indicates a lot of system calls being issued.
161 irq% Percentage of cpu time consumed for handling of device
163 interrupts.
164 softirq% Percentage of cpu time consumed for soft interrupt han‐
166 dling.
167 steal% Percentage of cpu time stolen by other virtual machines
169 running on the same hardware.
170 guest% Percentage of cpu time used by other virtual machines run‐
172 ning on the same hardware.
173 wait% Percentage of unused cpu time while at least one of the
175 processes in wait-state awaits completion of disk I/O.
176 idle% Percentage of unused cpu time because all processes are in
178 a wait-state but not waiting for disk-I/O.
179 The output for the flag -p contains the following values:
181 pswch/s Number of process switches (also called context switches)
183 per second on this cpu. A process switch occurs at the
184 moment that an active thread (i.e. the thread using a cpu)
185 enters a wait state or has used its time slice completely;
186 another thread will then be chosen to use the cpu.
187 devintr/s Number of hardware interrupts handled per second on this
189 cpu.
190 clones/s The number of new threads started per second.
192 loadavg1 Load average reflecting the average number of threads in
194 the runqueue or in non-interruptible wait state (usually
195 waiting for disk or tape I/O) during the last minute.
196 loadavg5 Load average reflecting the average number of threads in
198 the runqueue or in non-interruptible wait state (usually
199 waiting for disk or tape I/O) during the last 5 minutes.
200 loadavg15 Load average reflecting the average number of threads in
202 the runqueue or in non-interruptible wait state (usually
203 waiting for disk or tape I/O) during the last 15 minutes.
204 The output for the flag -P contains information about the processes and
206 threads:
207 clones/s The number of new threads started per second.
209 pexit/s
211 curproc Total number of processes present in the system.
213 curzomb Number of zombie processes present in the system.
215 thrrun Total number of threads present in the system in state
217 'running'.
218 thrslpi Total number of threads present in the system in state
220 'interruptible sleeping'.
221 thrslpu Total number of threads present in the system in state
223 'uninterruptible sleeping'.
224 The output for the flag -m contains information about the memory- and
226 swap-utilization:
227 memtotal Total usable main memory size.
229 memfree Available main memory size at this moment (snapshot).
231 buffers Main memory used at this moment to cache metadata-blocks
233 (snapshot).
234 cached Main memory used at this moment to cache data-blocks (snap‐
236 shot).
237 dirty Amount of memory in the page cache that still has to be
239 flushed to disk at this moment (snapshot).
240 slabmem Main memory used at this moment for dynamically allocated
242 memory by the kernel (snapshot).
243 swptotal Total swap space size at this moment (snapshot).
245 swpfree Available swap space at this moment (snapshot).
247 The output for the flag -s contains information about the frequency of
249 swapping:
250 pagescan/s Number of scanned pages per second due to the fact that
252 free memory drops below a particular threshold.
253 swapin/s The number of memory-pages the system read from the swap-
255 device per second.
256 swapout/s The number of memory-pages the system wrote to the swap-
258 device per second.
259 commitspc The committed virtual memory space i.e. the reserved vir‐
261 tual space for all allocations of private memory space for
262 processes.
263 commitlim The maximum limit for the committed space, which is by
265 default swap size plus 50% of memory size. The kernel only
266 verifies whether the committed space exceeds the limit if
267 strict overcommit handling is configured (vm.overcom‐
268 mit_memory is 2).
269 The output for the flags -l (LVM), -f (MD), and -d (hard disk) contains
271 the following columns per active unit:
272 disk Name.
274 busy Busy-percentage of the unit (i.e. the portion of time that
276 the device was busy handling requests).
277 read/s Number of read-requests issued per second on this unit.
279 KB/read Average number of Kbytes transferred per read-request for
281 this unit.
282 writ/s Number of write-requests issued per second on this unit.
284 KB/writ Average number of Kbytes transferred per write-request for
286 this unit.
287 avque Average number of requests outstanding in the queue during
289 the time that the unit is busy.
290 avserv Average number of milliseconds needed by a request on this
292 unit (seek, latency and data-transfer).
293 The output for the flag -i provides information about utilization of
295 network interfaces:
296 interf Name of interface.
298 busy Busy percentage for this interface. If the linespeed of
300 this interface could not be determined (for virtual inter‐
301 faces or in case that atop or atopsar had no root-privi‐
302 leges), a question mark is shown.
303 ipack/s Number of packets received from this interface per second.
305 opack/s Number of packets transmitted to this interface per second.
307 iKbyte/s Number of Kbytes received from this interface per second.
309 oKbyte/s Number of Kbytes transmitted via this interface per second.
311 imbps/s Effective number of megabits received per second.
313 ombps/s Effective number of megabits transmitted per second.
315 maxmbps/s Linespeed as number of megabits per second. If the line‐
317 speed could not be determined (for virtual interfaces or in
318 case that atop or atopsar had no root-privileges), value 0
319 is shown.
320 The linespeed is followed by the indication 'f' (full
321 duplex) or 'h' (half duplex).
322 The output for the flag -I provides information about the failures that
324 were detected for network interfaces:
325 interf Name of interface.
327 ierr/s Number of bad packets received from this interface per sec‐
329 ond.
330 oerr/s Number of times that packet transmission to this interface
332 failed per second.
333 coll/s Number of collisions encountered per second while transmit‐
335 ting packets.
336 idrop/s Number of received packets dropped per second due to lack
338 of buffer-space in the local system.
339 odrop/s Number of transmitted packets dropped per second due to
341 lack of buffer-space in the local system.
342 iframe/s Number of frame alignment-errors encountered per second on
344 received packets.
345 ocarrier/s Number of carrier-errors encountered per second on trans‐
347 mitted packets.
348 The output for the flag -w provides information about the utilization
350 of the IPv4-layer (formal SNMP-names between brackets):
351 inrecv/s Number of IP datagrams received from interfaces per second,
353 including those received in error (ipInReceives).
354 outreq/s Number of IP datagrams that local higher-layer protocols
356 supplied to IP in requests for transmission per second
357 (ipOutRequests).
358 indeliver/s Number of received IP datagrams that have been succesfully
360 delivered to higher protocol-layers per second (ipInDeliv‐
361 ers).
362 forward/s Number of received IP datagrams per second for which this
364 entity was not their final IP destination, as a result of
365 which an attempt was made to forward (ipForwDatagrams).
366 reasmok/s Number of IP datagrams succesfully reassembled per second
368 (ipReasmOKs).
369 fragcreat/s Number of IP datagram fragments generated per second at
371 this entity (ipFragCreates).
372 The output for the flag -W provides information about the failures that
374 were detected in the IPv4-layer (formal SNMP-names between brackets):
375 in: dsc/s Number of input IP datagrams per second for which no prob‐
377 lems were encountered to prevent their continued processing
378 but that were discarded, e.g. for lack of buffer space
379 (ipInDiscards).
380 in: hder/s Number of input IP datagrams per second discarded due to
382 errors in the IP header (ipInHdrErrors).
383 in: ader/s Number of input IP datagrams per second discarded because
385 the IP address in the destination field was not valid to be
386 received by this entity (ipInAddrErrors).
387 in: unkp/s Number of inbound packets per second that were discarded
389 because of an unknown or unsupported protocol (ipInUnknown‐
390 Protos).
391 in: ratim/s Number of timeout-situations per second while other frag‐
393 ments were expected for successful reassembly (ipReasmTime‐
394 out).
395 in: rfail/s Number of failures detected per second by the IP reassembly
397 algorithm (ipReasmFails).
398 out: dsc/s Number of output IP datagrams per second for which no prob‐
400 lems were encountered to prevent their continued processing
401 but that were discarded, e.g. for lack of buffer space
402 (ipOutDiscards).
403 out: nrt/s Number of IP datagrams per second discarded because no
405 route could be found (ipOutNoRoutes).
406 The output for the flag -y provides information about the general uti‐
408 lization of the ICMPv4-layer and some information per type of ICMP-mes‐
409 sage (formal SNMP-names between brackets):
410 intot/s Number of ICMP messages (any type) received per second at
412 this entity (icmpInMsgs).
413 outtot/s Number of ICMP messages (any type) transmitted per second
415 from this entity (icmpOutMsgs).
416 inecho/s Number of ICMP Echo (request) messages received per second
418 (icmpInEchos).
419 inerep/s Number of ICMP Echo-Reply messages received per second
421 (icmpInEchoReps).
422 otecho/s Number of ICMP Echo (request) messages transmitted per sec‐
424 ond (icmpOutEchos).
425 oterep/s Number of ICMP Echo-Reply messages transmitted per second
427 (icmpOutEchoReps).
428 The output for the flag -Y provides information about other types of
430 ICMPv4-messages (formal SNMP-names between brackets):
431 ierr/s Number of ICMP messages received per second but determined
433 to have ICMP-specific errors (icmpInErrors).
434 isq/s Number of ICMP Source Quench messages received per second
436 (icmpInSrcQuenchs).
437 ird/s Number of ICMP Redirect messages received per second (icmp‐
439 InRedirects).
440 idu/s Number of ICMP Destination Unreachable messages received
442 per second (icmpInDestUnreachs).
443 ite/s Number of ICMP Time Exceeded messages received per second
445 (icmpOutTimeExcds).
446 oerr/s Number of ICMP messages transmitted per second but deter‐
448 mined to have ICMP-specific errors (icmpOutErrors).
449 osq/s Number of ICMP Source Quench messages transmitted per sec‐
451 ond (icmpOutSrcQuenchs).
452 ord/s Number of ICMP Redirect messages transmitted per second
454 (icmpOutRedirects).
455 odu/s Number of ICMP Destination Unreachable messages transmitted
457 per second (icmpOutDestUnreachs).
458 ote/s Number of ICMP Time Exceeded messages transmitted per sec‐
460 ond (icmpOutTimeExcds).
461 The output for the flag -u provides information about the utilization
463 of the UDPv4-layer (formal SNMP-names between brackets):
464 indgram/s Number of UDP datagrams per second delivered to UDP users
466 (udpInDatagrams).
467 outdgram/s Number of UDP datagrams transmitted per second from this
469 entity (udpOutDatagrams).
470 inerr/s Number of received UDP datagrams per second that could not
472 be delivered for reasons other than the lack of an applica‐
473 tion at the destination port (udpInErrors).
474 noport/s Number of received UDP datagrams per second for which there
476 was no application at the destination port (udpNoPorts).
477 The output for the flag -z provides information about the utilization
479 of the IPv6-layer (formal SNMP-names between brackets):
480 inrecv/s Number of input IPv6-datagrams received from interfaces per
482 second, including those received in error (ipv6IfStatsInRe‐
483 ceives).
484 outreq/s Number of IPv6-datagrams per second that local higher-layer
486 protocols supplied to IP in requests for transmission
487 (ipv6IfStatsOutRequests). This counter does not include
488 any forwarded datagrams.
489 inmc/s Number of multicast packets per second that have been
491 received by the interface (ipv6IfStatsInMcastPkts).
492 outmc/s Number of multicast packets per second that have been
494 transmitted to the interface (ipv6IfStatsOutMcastPkts).
495 indeliv/s Number of IP datagrams succesfully delivered per second to
497 IPv6 user-protocols, including ICMP (ipv6IfStatsInDeliv‐
498 ers).
499 reasmok/s Number of IPv6 datagrams succesfully reassembled per second
501 (ipv6IfStatsReasmOKs).
502 fragcre/s Number of IPv6 datagram fragments generated per second at
504 this entity (ipv6IfStatsOutFragCreates).
505 The output for the flag -Z provides information about the failures that
507 were detected in the IPv6-layer (formal SNMP-names between brackets):
508 in: dsc/s Number of input IPv6 datagrams per second for which no
510 problems were encountered to prevent their continued pro‐
511 cessing but that were discarded, e.g. for lack of buffer
512 space (ipv6IfStatsInDiscards).
513 in: hder/s Number of input datagrams per second discarded due to
515 errors in the IPv6 header (ipv6IfStatsInHdrErrors).
516 in: ader/s Number of input datagrams per second discarded because the
518 IPv6 address in the destination field was not valid to be
519 received by this entity (ipv6IfStatsInAddrErrors).
520 in: unkp/s Number of locally-addressed datagrams per second that were
522 discarded because of an unknown or unsupported protocol
523 (ipv6IfStatsInUnknownProtos).
524 in: ratim/s Number of timeout-situations per second while other IPv6
526 fragments were expected for successful reassembly
527 (ipv6ReasmTimeout).
528 in: rfail/s Number of failures detected per second by the IPv6 reassem‐
530 bly-algorithm (ipv6IfStatsReasmFails).
531 out: dsc/s Number of output IPv6 datagrams per second for which no
533 problems were encountered to prevent their continued pro‐
534 cessing but that were discarded, e.g. for lack of buffer
535 space (ipv6IfStatsOutDiscards).
536 out: nrt/s Number of IPv6 datagrams per second discarded because no
538 route could be found (ipv6IfStatsInNoRoutes).
539 The output for the flag -k provides information about the general uti‐
541 lization of the ICMPv6-layer and some information per type of ICMP-mes‐
542 sage (formal SNMP-names between brackets):
543 intot/s Number of ICMPv6 messages (any type) received per second at
545 the interface (ipv6IfIcmpInMsgs).
546 outtot/s Number of ICMPv6 messages (any type) transmitted per second
548 from this entity (ipv6IfIcmpOutMsgs).
549 inerr/s Number of ICMPv6 messages received per second that had
551 ICMP-specific errors, such as bad ICMP checksums, bad
552 length, etc (ipv6IfIcmpInErrors).
553 innsol/s Number of ICMP Neighbor Solicit messages received per sec‐
555 ond (ipv6IfIcmpInNeighborSolicits).
556 innadv/s Number of ICMP Neighbor Advertisement messages received per
558 second (ipv6IfIcmpInNeighborAdvertisements).
559 otnsol/s Number of ICMP Neighbor Solicit messages transmitted per
561 second (ipv6IfIcmpOutNeighborSolicits).
562 otnadv/s Number of ICMP Neighbor Advertisement messages transmitted
564 per second (ipv6IfIcmpOutNeighborAdvertisements).
565 The output for the flag -K provides information about other types of
567 ICMPv6-messages (formal SNMP-names between brackets):
568 iecho/s Number of ICMP Echo (request) messages received per second
570 (ipv6IfIcmpInEchos).
571 ierep/s Number of ICMP Echo-Reply messages received per second
573 (ipv6IfIcmpInEchoReplies).
574 oerep/s Number of ICMP Echo-Reply messages transmitted per second
576 (ipv6IfIcmpOutEchoReplies).
577 idu/s Number of ICMP Destination Unreachable messages received
579 per second (ipv6IfIcmpInDestUnreachs).
580 odu/s Number of ICMP Destination Unreachable messages transmitted
582 per second (ipv6IfIcmpOutDestUnreachs).
583 ird/s Number of ICMP Redirect messages received per second
585 (ipv6IfIcmpInRedirects).
586 ord/s Number of ICMP Redirect messages transmitted per second
588 (ipv6IfIcmpOutRedirect).
589 ite/s Number of ICMP Time Exceeded messages received per second
591 (ipv6IfIcmpInTimeExcds).
592 ote/s Number of ICMP Time Exceeded messages transmitted per sec‐
594 ond (ipv6IfIcmpOutTimeExcds).
595 The output for the flag -U provides information about the utilization
597 of the UDPv6-layer (formal SNMP-names between brackets):
598 indgram/s Number of UDPv6 datagrams per second delivered to UDP users
600 (udpInDatagrams),
601 outdgram/s Number of UDPv6 datagrams transmitted per second from this
603 entity (udpOutDatagrams),
604 inerr/s Number of received UDPv6 datagrams per second that could
606 not be delivered for reasons other than the lack of an
607 application at the destination port (udpInErrors).
608 noport/s Number of received UDPv6 datagrams per second for which
610 there was no application at the destination port (udpNo‐
611 Ports).
612 The output for the flag -t provides information about the utilization
614 of the TCP-layer (formal SNMP-names between brackets):
615 insegs/s Number of received segments per second, including those
617 received in error (tcpInSegs).
618 outsegs/s Number of transmitted segments per second, excluding those
620 containing only retransmitted octets (tcpOutSegs).
621 actopen/s Number of active opens per second that have been supported
623 by this entity (tcpActiveOpens).
624 pasopen/s Number of passive opens per second that have been supported
626 by this entity (tcpPassiveOpens).
627 nowopen Number of connections currently open (snapshot), for which
629 the state is either ESTABLISHED or CLOSE-WAIT (tcpCur‐
630 rEstab).
631 The output for the flag -T provides information about the failures that
633 were detected in the TCP-layer (formal SNMP-names between brackets):
634 inerr/s Number of received segments per second received in error
636 (tcpInErrs).
637 retrans/s Number of retransmitted segments per second (tcpRe‐
639 transSegs).
640 attfail/s Number of failed connection attempts per second that have
642 occurred at this entity (tcpAttemptFails).
643 estabreset/s
645 Number of resets per second that have occurred at this
646 entity (tcpEstabResets).
647 outreset/s Number of transmitted segments per second containing the
649 RST flag (tcpOutRsts).
650 The output for the flag -O provides information about the top-3 of pro‐
652 cesses with the highest processor consumption:
653 pid Process-id (if zero, the process has exited while the pid
655 could not be determined).
656 command The name of the process.
658 cpu% The percentage of cpu-capacity being consumed. This value
660 can exceed 100% for a multithreaded process running on a
661 multiprocessor machine.
662 The output for the flag -G provides information about the top-3 of pro‐
664 cesses with the highest memory consumption:
665 pid Process-id (if zero, the process has exited while the pid
667 could not be determined).
668 command The name of the process.
670 mem% The percentage of resident memory-utilization by this
672 process.
673 The output for the flag -D provides information about the top-3 of pro‐
675 cesses that issue the most read and write accesses to disk:
676 pid Process-id (if zero, the process has exited while the pid
678 could not be determined).
679 command The name of the process.
681 dsk% The percentage of read and write accesses related to the
683 total number of read and write accesses issued on disk by
684 all processes, so a high percentage does not imply a high
685 disk load on system level.
686 The output for the flag -N provides information about the top-3 of pro‐
688 cesses that issue the most socket transfers for IPv4/IPv6:
689 pid Process-id (if zero, the process has exited while the pid
691 could not be determined).
692 command The name of the process.
694 net% The percentage of socket transfers related to the total
696 number of transfers issued by all processes, so a high per‐
697 centage does not imply a high network load on system level.
698
700 To see today's cpu-activity so far (supposed that atop is logging in
701 the background):
702 atopsar
704 To see the memory occupation for January 2, 2010 between 10:00 and
706 12:30 (supposed that atop has been logging daily in the background):
707 atopsar -m -r /var/log/atop_20100102 -b 10:00 -e 12:30
709 or
711 atopsar -m -r 20100102 -b 10:00 -e 12:30
713 or, suppose it is January 5, 2010 at this moment
715 atopsar -m -r yyy -b 10:00 -e 12:30
717 Write a logfile with atop to record the system behaviour for 30 minutes
719 (30 samples of one minute) and produce all available reports after‐
720 wards:
721 atop -w /tmp/atoplog 60 30
723 atopsar -A -r /tmp/atoplog
725 To watch TCP activity evolve for ten minutes (10 samples with sixty
727 seconds interval):
728 atopsar -t 60 10
730 To watch the header-lines ('_' as last character) of all reports with
732 only the detail-lines showing critical resource consumption (marker '*'
733 or '+' as last character):
734 atopsar -AM | grep '[_*+]$'
736
738 /etc/atoprc
739 Configuration file containing system-wide default values (mainly
740 flags). See related man-page.
741 ~/.atoprc
743 Configuration file containing personal default values (mainly
744 flags). See related man-page.
745 /var/log/atop/atop_YYYYMMDD
747 Daily data file, where YYYYMMDD are digits representing the date.
748
750 atop(1), atoprc(5),
751 http://www.atoptool.nl
752
754 Gerlof Langeveld (gerlof.langeveld@atoptool.nl)
755AT Computing April 2010 ATOPSAR(1)