On Sat, 2019-03-16 at 12:10 +0100, Jakub Wilk wrote: > You can use %c in core_pattern to get the soft limit of the crashing > process. > > (Hmm, it's not documented what's the value you get when there's no > limit...)
I got 0xffffffffffffffff on amd64 when it was set to unlimited, which corresponds to RLIM_INFINITY. Not sure how to get RLIM_INFINITY in shell though but I guess that it is close enough to infinity that it doesn't matter and using the value would be fine. Now I wonder how to add %c to the core_pattern and also deal with old versions of Linux. Perhaps instead of just passing parameters to the dumper, they should be qualified with options. |/usr/lib/corekeeper/dump --dumpable %d --user %u --group %g --limit %c --pid %p --signal %s --time %t --hostname %h --executable %E The %d option is numeric or missing so that should be easy to handle by checking if the option parameter is numeric. However the %h %E %e options could contain spaces so perhaps they should just be added after an options termination option and the dumper script would then just append the remaining arguments to the core name. |/usr/lib/corekeeper/dump --dumpable %d --user %u --group %g --limit %c --pid %p --signal %s --time %t -- %h %E Any thoughts? -- bye, pabs https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
