Right now the kdump action is executed last for all configured actions, but it still fires before a 'normal' rig termination.
Instead, if a kdump is requested, rig should go through it's normal cleanup procedure, and trigger kdump after any other data has been collected into a tar archive.
Right now the kdump action is executed last for all configured actions, but it still fires before a 'normal' rig termination.
Instead, if a kdump is requested, rig should go through it's normal cleanup procedure, and trigger kdump after any other data has been collected into a tar archive.