ATOPCAT(1)
π ATOPCAT β the manual, but make it slay π
okay bestie, gather round, because atopcat is genuinely one of those little tools that's lowkey iconic once you get it. It's a general commands manual page situation, and I'm gonna walk you through every single crumb. no cap. π«Ά
β¨ NAME β¨
atopcat β concatenate raw log files to stdout
πΈ SYNOPSIS πΈ
atopcat [-dv] rawfile [rawfile]...
π¦ DESCRIPTION π¦
okay so here's the vibe: atopcat takes several raw log files and smushes them together into one single stream, and that stream goes straight to stdout. that's it. that's the whole job. π
and because it's stdout, you have options, bestie:
- redirect stdout into a file and boom, you've merged multiple raw log files into one bigger file β¨
- or pipe that merged data directly into
atoporatopsarand it just works π
Both paths are valid, both are valid, and both are literally the point of this program.
π Options
-dβ dry-run: it reads the logfile(s) but does not generate any output on stdout. it's giving "I'm just here to observe, not to participate" π-vβ verbose: prints one line per sample. that line contains the date/time, the interval length in seconds, the compressed length of the system-level information, the compressed length of the process-level information, the compressed length of the cgroup-level information, and the compressed length of the PID list. yes that's a lot of numbers per line, and yes, she's thorough π
π₯ EXAMPLES π₯
concat five contiguous working days into one new raw log file and view the week interactively
atopcat /var/log/atop/atop_2024021[0-4] > week_2024_7
atop -r week_2024_7
concat a week of raw log files and view it interactively
atopcat /var/log/atop/atop_2024021[0-6] | atop -r -
heads up bestie: since atop reads from a pipe here, previous intervals can not be retrieved while viewing. it's a one-way stream situation, no rewind. π
concat all raw log files of January 2024 and get parsable output about CPU utilization
atopcat /var/log/atop/atop_202401?? | atop -r - -PCPU
concat the daily raw log files of February 3 and 4, and generate a report about memory utilization from 14:00h on the first day till 11:00h on the second day
atopcat /var/log/atop/atop_2024020[34] |
atopsar -m -r - -b 202402031400 -e 202402041100
repair a raw log file whose last interval wasn't completely written
atopcat /var/log/atop/atop_20240303 > /tmp/repaired
like, say you intend to expand the file with new samples later β this is the move. π οΈ
β οΈ in that last case, atopcat reports that the input file is incomplete and stops after the last consistent sample. it knows when something's off and it will not pretend otherwise. periodt.
π SEE ALSO π
atop(1), atopsar(1), atophide(1), atopconvert(1)
π AUTHOR π
Gerlof Langeveld (gerlof.langeveld@atoptool.nl)
and that's the whole page, bestie. this one came out of the Linux scene back in January 2024, and the tool lives at version ATOPCAT(1) β so go forth, concat those raw logs, and remember: she's small, she's simple, and she absolutely ate. π β¨π¦
π¦ where this page comes from
- alpine 3.22: atop-doc 2.11.1-r0 Β· GPL-2.0-or-later
- alpine 3.23: atop-doc 2.12.1-r0 Β· GPL-2.0-or-later
- alpine 3.24: atop-doc 2.12.1-r0 Β· GPL-2.0-or-later
- arch rolling: atop 2.13.0-1 Β· GPL-2.0-or-later
- debian trixie: atop 2.11.1-3 Β· GPL-2.0-or-later
- nixos 26.05: atop 2.12.1
- nixpkgs unstable: atop 2.13.0
- opensuse-leap 16.0: atop 2.11.1-bp160.1.4 Β· GPL-2.0-only
- opensuse-leap 16.0: atop 2.11.1-bp160.1.4 Β· GPL-2.0-only
- opensuse-leap 16.0: atop 2.11.1-bp160.1.4 Β· GPL-2.0-only
- opensuse-leap 16.0: atop 2.11.1-bp160.1.4 Β· GPL-2.0-only
- ubuntu questing: atop 2.11.1-3
- ubuntu resolute: atop 2.12.1-1 Β· GPL-2.0-or-later
- ubuntu stonking: atop 2.13.0-1 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms