On 05/04/2020 09.42, Per Jessen wrote:
Carlos E.R. wrote:
Sure, like I said, "for what it's worth". I'll wait 24hours and report back. That it takes a day before the problem manifests itself does seem indicative of something not being cleaned up.
Yes, but what?
Telcontar:~ # ulimit -a [snip] stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 1850 ^^^^ That's very low.
Well, it wasn't till firefox opened 400 threads :-D The computer maximum seems to be 32k something, not a longint.
Ah. Here: /etc/security/limits.conf
FWIW, that file is empty on my Leap 15.1 system. As Andrei already suggested, something or someone changed that file.
That file here is old. Maybe is empty now, but it was not in some past. At some time there was a problem or scare about fork bombs and I reduced the number.
limits.conf comes with pam - maybe check if you have any /etc/security/limits.conf.* ?
Nope. I have older copies of the file, dated back to 2009, everything commented out. Had this paragraph: #<domain> <type> <item> <value> #* soft core 0 #* hard rss 10000 #@student hard nproc 20 #@faculty soft nproc 20 #@faculty hard nproc 50 #ftp hard nproc 0 #@student - maxlogins 4 It was the same on year 2005, version 10.1, and later till 13.1 (2016?) - so I don't see when was the "fork bomb". Later. Maybe Feb 5, 2018. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)