Carlos E. R. wrote:
On Friday, 2017-08-18 at 13:42 +0200, Carlos E. R. wrote:
cer@Isengard:~> ulimit -c 0
It is already zero. Well, the limit is set now in the script.
Well, it is dumping core right now, it did not work. The app was using about 3 GB, so it is running now compressing those 3 GB of nothing, for 20 minutes already. Oh, finished now. 1.8 GB compressed.
On my leap423 test system, at first it seems I have the opposite behaviour - (dump is just some code that tries to write to address 0x0). per@office36:~> ulimit -c 0 per@office36:~> ./dump Segmentation fault (core dumped) per@office36:~> coredumpctl No coredumps found. Okay. per@office36:~> ulimit -c unlimited per@office36:~> ./dump Segmentation fault (core dumped) per@office36:~> coredumpctl No coredumps found. Weird. switching to root - office36:~ # coredumpctl TIME PID UID GID SIG PRESENT EXE Sun 2017-08-20 18:41:36 CEST 9394 1000 100 11 * /home/per/dump Sun 2017-08-20 18:44:41 CEST 9420 1000 100 11 * /home/per/dump For one thing, 'ulimit' indeed seems to be ignored, for another why can't I see my own coredumps? -- Per Jessen, Zürich (21.4°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