minicoredumper.cfg.json - the main configuration file for
is the main configuration file for
(1). It serves 2 purposes:
- define where dumped files should be located
- specify various minicoredumper(1) recepts for
The file uses the JSON format. The options are:
- (string) The root directory where the dumped data will be
stored. The dump files will be stored in a sub-directory using the
- (array) A set of conditions, where each condition can
specify its own recept file. See CONDITIONS for configuration
options for a condition.
A condition can contain any combination of these options:
- (string) The full path to the binary being executed as
returned by readlink(2).
- (string) The basename of the command that was run (the 7th
argument of the minicoredumper(1) call).
- (string) The full path to the recept file to use if this
can contain the * character for wildcard
The conditions are checked to find a match in the order specified. The first
match will cause the minicoredumper to use the recept for that condition. If
no conditions match, the minicoredumper will exit and no core
will be generated.
are not specified for a condition, they will
use a default value "*".
is not specified for a condition, the built-in minicoredumper
defaults are used.
have a "logical AND" relationship. A
"logical OR" behavior can be achieved by specifying one condition
with only exe
and another condition with only comm
The exact path where data is dumped is logged to syslog
If an 8th argument of minicoredumper
(1) is provided, the name and
location of this file will depend on that value.
Here is an example configuration file:
In this example, dumped data will be stored in a directory named:
For example, if there is a symbolic link:
and the user runs "example_app" and it crashes, the newly created
files could be found here:
The example above contains 4 conditions that will be checked in order.
The first condition will match if the binary "*/my_example_app" caused
the core dump. It will use the recept file:
The second condition will match if the basename of the command is
"example_app". It will also use the recept file:
The third condition will match for any binaries under "/bin/*". It
will use the built-in minicoredumper
The fourth condition will match everything. It will use the recept file:
In the example where the user runs "example_app", the first condition
will match since example_app is a symbolic link to
A minimal (yet still useful) configuration file could look like this:
The DiaMon Workgroup: <http://www.diamon.org>