1cas.conf(5) File Formats Manual cas.conf(5)
2
3
4
6 cas.conf - Cas configuration file.
7
9 cas.conf is the configuration file for cas.
10
12 casuser: (Required) User to run cas, recommended to run as someone
13 other than root.
14
15 sshkey: (Required) Used for ssh negotiation, these are generated with
16 ssh-keygen.
17
18 kernels: (Required) Describes the location of where kernel-debuginfo
19 packages are to be stored. This can range anywhere from an nfs mount,
20 samba share, local disk or any other type of media the cas server can
21 access.
22
23 regexExcludeDir: Directories that may be within the search path that
24 doesn’t need to be included. This is a shell format so globs like
25 */*/data are accepted.
26
27 regexExcludeFile: Any files that need to be excluded from the search
28 path. This is also a shell format */*/badfile.txt.
29
30 regexType: (Required) Defines the regex syntax to use within find.
31 Doing a man find and searching for regextype will give you the allow‐
32 able syntaxess.
33
34 rpmFilters: (Required) This is a emacs based regular expression which
35 is essentially passed to a find command to locate the various kernel-
36 debuginfo packages defined in kernels directive.
37
38 debugLevel: As the name suggest it will set the debug level for CAS
39 output. Currently the only accepted values are DEBUG|INFO.
40
41 workDirectory: (Required) Defines where all processed cores will be
42 placed. This mount point will need to have the most storage assigned to
43 it. Depending on how many cores are processed in a given timeframe this
44 area will fill up quickly.
45
46 smtphost: If wanting output of CAS processing email to a certain
47 address this directive needs to be set. Note that the mail server
48 should not require smtp authentication.
49
50 database: (Required) Define where the sqlite database will reside. Note
51 the casuser will need to have read/write access to this database.
52
53
55 purgeLimit: Define amount of day(s) back wish to keep physical data on
56 system.
57
58 autoPurge: Yes/No setting if wanting cas-admin to auto purge stale data
59 on each run.
60
61
63 crash_32: Primarily used on x86_64 systems to process x86 cores. If x86
64 version of crash is installed this directive can be set to the crash
65 binary and CAS will automatically process x86 cores on a x86_64
66 machine. Note this is only available if the CAS server is a x86_64
67 machine.
68
69 buffersize: Extend the read buffer when analyzing a core for a time‐
70 stamp. Note this is normally needed for itanium cores, otherwise, the
71 default is fine.
72
73
75 /etc/cas.conf
76
78 cas(1)
79 cas-admin(1)
80 Full documentation located in /usr/share/doc/cas-<version>.
81
82
83
84cas configuration file CAS cas.conf(5)