Carlos E. R. wrote:
On 2017-08-18 20:17, David Haller wrote:
Hello,
On Fri, 18 Aug 2017, Carlos E. R. wrote:
cer@Isengard:~> ulimit -c 0
It is already zero. Well, the limit is set now in the script.
Try 'ulimit -H -c 0' or even:
I don't find -H in man bash :-? Ah, I see it now, it is embedded in the text section. Hard limit.
As I set the limit as user, it will be soft anyway.
echo 0 > /proc/self/coredump_filter ./some_program
Read up on the latter in /usr/src/linux/Documentation/filesystems/proc.txt
+++--------------------- 3.4 /proc/<pid>/coredump_filter - Core dump filtering settings --------------------------------------------------------------- When a process is dumped, all anonymous memory is written to a core file as long as the size of the core file isn't limited. But sometimes we don't want to dump some memory segments, for example, huge shared memory or DAX. Conversely, sometimes we want to save file-backed memory segments into a core file, not only the individual files.
/proc/<pid>/coredump_filter allows you to customize which memory segments will be dumped when the <pid> process is dumped. coredump_filter is a bitmask of memory types. If a bit of the bitmask is set, memory segments of the corresponding memory type are dumped, otherwise they are not dumped. ---------------------++-
I see. But it applies to all programs.
When you apply it to /proc/self/coredump_filter, it only affects the current process (and children). -- Per Jessen, Zürich (20.2°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org