1RECAP(8) System Manager's Manual RECAP(8)
2
3
4
6 recap - dumps periodic information about running applications and
7 resource usage
8
10 recap [OPTION]
11
13 recap is a user-configurable script that can be run once, or run peri‐
14 odically out of cron or systemd.timers to dump information about run‐
15 ning processes and resource usage. It's useful on servers that have
16 periodic, mysterious performance anomalies for tracking down what may
17 be going on at the time of any particular incident.
18
19 The values for which reports are generated and how many reports are
20 stored can be overridden in /etc/recap.conf. The output files from the
21 script are written to BASEDIR.
22
23 -B, --backup
24 This will perform a "backup". It will copy the latest log files
25 from the last execution to the "backups" directory inside
26 BASEDIR. The files will be identified by a timestamp in the
27 name.
28
29 -S, --snapshot
30 This will perform a "snapshot" report. It will generate a set of
31 output files in the "snapshot" directory inside BASEDIR outside
32 of the standard rotation. The files will be identified by a
33 timestamp in the name.
34
35 -V, --version
36 Print version and exit.
37
38
39 FILES
40 /etc/recap.conf
41 /etc/cron.d/recap
42 /usr/lib/systemd/system/recap.{service,timer} - Unit files for running recap periodically.
43 /usr/lib/systemd/system/recap-onboot.{service,timer} - Unit files for running recap on boot.
44
45
47 Bugs and issues to be submitted via github <https://github.com/racker‐
48 labs/recap/issues>.
49
50
52 The recap scripts are maintained by Rackspace, the list of contributors
53 is available at https://github.com/rackerlabs/recap/blob/mas‐
54 ter/CHANGELOG.md#contributors.
55
57 recap.conf(5), recaplog(8), crontab(5), systemd.timer(5)
58
59
60
61 Aug 18, 2017 RECAP(8)