Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Need capability to select, via YAML, if crash dump should be enabled #78

Closed
jeffaco opened this issue Sep 4, 2018 · 1 comment
Closed

Need capability to select, via YAML, if crash dump should be enabled #78

jeffaco opened this issue Sep 4, 2018 · 1 comment
Assignees
@schaefi
Labels
enhancement New feature or request P1 Prio 1 indicates next issue to work on

Comments

@jeffaco
Copy link
Collaborator

jeffaco commented Sep 4, 2018

On VLI systems with 12+TB of RAM, crash dumps can take quite a while.

Is it possible, within the YAML file, to select if crash dumps are enabled or disabled? Perhaps something like:

crash-dump: enabled | disabled

If not specified in YAML, then crash dump should be as is (enabled).
@jeffaco jeffaco added the enhancement New feature or request label Sep 4, 2018
@schaefi schaefi added the P1 Prio 1 indicates next issue to work on label Sep 10, 2018
@schaefi
Copy link
Collaborator

schaefi commented Sep 10, 2018 •
edited
Loading

I'll change the setup of crash dump to be in its own section. It will look like this:

crash_dump:
  activate: true
  crash_kernel_low: 80
  crash_kernel_high: 160

you can control with the activate switch if the crash dump setup is performed or not. Only if there is a setup saying activate: false we will skip the crash dump setup. In any other case even without a crash_dump section or no information about high and low values we will setup the crash dump service.

@schaefi schaefi self-assigned this Sep 10, 2018
schaefi added a commit that referenced this issue Sep 11, 2018
@schaefi
Allow to activate/deactivate the crash dump setup
47b82b5 
The crash dump setup deserves its own section containing
the optional high/low values as well as a new switch to
control the activation of the setup process.
This Fixes #78
@schaefi schaefi mentioned this issue Sep 11, 2018
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@schaefi schaefi

Labels
enhancement New feature or request P1 Prio 1 indicates next issue to work on
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@schaefi @jeffaco