On Sat, 17 Aug 2019 08:26:01 +0200 "Carlos E. R." <robin.listas@telefonica.net> wrote:
On 16/08/2019 19.18, Andrei Borzenkov wrote:
Отправлено с iPhone
16 авг. 2019 г., в 18:58, Carlos E.R. <robin.listas@gmx.es> написал(а):
On 16/08/2019 15.26, Adam Majer wrote:
On 8/16/19 12:54 PM, Carlos E. R. wrote: # Avoid huge dump core ops - doesn't work on Leap 42.2 ulimit -H -c 0 echo 0 > /proc/self/coredump_filter program
Suddenly, after an update applied yesterday, I get:
/home/cer/bin/fusion: line 81: ulimit: core file size: cannot modify limit: Invalid argument
I think the bug is that hard limit cannot be smaller than soft limit.
# ulimit -H -c unlimited
# ulimit -c unlimited
# ulimit -H -c 0 -bash: ulimit: core file size: cannot modify limit: Invalid argument
# ulimit -c 0 # ulimit -H -c 0 # ulimit -H -c 0
Hope this helps.
Wow! I see. Thank you and Dave H. :-)
And how exactly does it answer your question? Which was “The issue is finding out why ulimit is complaining now, when a month ago it didn't. What has changed and why?”
What has changed, I understand, is that now hard limit can not be smaller than soft limit, and **both have to be applied separately instead of simultaneouzsly. This is what has changed, that they have to be applied separately in certain order.**
No, you can change them together. You just can't reduce the hard limit below the soft limit.
You seem to apply double standard, where you scorn at one reply that does not answer your question but praise another.
Wow.
Also this setting is mostly irrelevant in openSUSE which is using systemd core manager by default so kernel ignores these limits.
No, it doesn't.
The coredumps of this process stopped when I first applied this command a year or two ago.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org