+1
−1
Loading
As stated in the core(5) the RLIMIT_CORE is not enforced when kernel is piping core to the collector, hence it will be written out even when it's set to 0. Instead of playing nice and checking the validity of RLIMIT_CORE, simply ignore it and apply our own limit (2GB). This is done for convenience and to make sure that any changes to the way how given distro applies limits (see fedora37) to the processes doesn't affect our core collection. Signed-off-by:Michal Berger <michal.berger@intel.com> Change-Id: Iab8757f548f2a4f0f4b27b4ce66b0a4a84ed2579 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/15994 Reviewed-by:
Konrad Sztyber <konrad.sztyber@intel.com> Reviewed-by:
Jim Harris <james.r.harris@intel.com> Tested-by:
SPDK CI Jenkins <sys_sgci@intel.com>