Re: amusing logwatch messages

2021-11-11 Thread Ed Greshko
On 12/11/2021 01:01, Tom Horsley wrote: Never seen this one before: **Unmatched Entries** app-glib-google\x2dchrome-509173.scope: No PIDs left to attach to the scope's control group, refusing: Success: 1 Time(s) I'm particularly fond of the "Success" at the end :-). But considering that

Re: amusing logwatch messages

2021-11-11 Thread Roger Heflin
I am not sure a fork bomb would run you out of pids or not anymore with the new limit. at 16 pages per forked process the 4M pids takes 256G of ram (to just exist), and I really doubt that even a fork bomb will only use a 16 pages per process additional, so the fork bomb is more likely to now OOM/

Re: amusing logwatch messages

2021-11-11 Thread Joe Zeff
On 11/11/21 10:01 AM, Tom Horsley wrote: I'm particularly fond of the "Success" at the end :-). But considering that PID numbers now go up into the millions, I wonder how anything could be out of pids. I doubt that this is the answer here, but a fork bomb would eventually manage it. _

amusing logwatch messages

2021-11-11 Thread Tom Horsley
Never seen this one before: **Unmatched Entries** app-glib-google\x2dchrome-509173.scope: No PIDs left to attach to the scope's control group, refusing: Success: 1 Time(s) I'm particularly fond of the "Success" at the end :-). But considering that PID numbers now go up into the millions, I