-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2017-08-20 at 18:50 +0200, Per Jessen wrote:
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.
...
For one thing, 'ulimit' indeed seems to be ignored, for another why can't I see my own coredumps?
Just found a post from Andrei Borzenkov on 2 Dec 2016, subj "leap422 - where is my core dump?" +++..................
If core exceeds ulimit -c, it is not created at all and systemd-coredump does not see it. So how exactly it would be useful here?
I stay corrected. Linux kernel ignores ulimit -c when core_pattern is set to pipe; so yes, it is useful and is actually honored by systemd as of version 229 upstream. If this is not included in Leap 42.2, it is good candidate for bug report. ..................++- - -- Cheers, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlmmuWAACgkQtTMYHG2NR9UU0QCfV8QSo9u11VVK30IcoJbiY91X 6T8AoIeuUJqpAo1uxDkXVWq4Cli6UnYc =0pGp -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org