On Sat, Dec 3, 2022 at 12:08 PM Stuart Henderson <stu.li...@spacehopper.org> wrote: > > On 2022-12-03, Sven F. <sven.falem...@gmail.com> wrote: > > Bit sad the kernel stopped working thought. > > AFAIK the main options available at that point are: > > deadlocks waiting for resources > detect the problem and randomly kill processes (e.g. linux oom killer) > detect the problem and panic
i was idealizing keep enough resource for critical process like * shell * sshd > > There isn't really a lot else it could do, it has already done things > like reduce buffer cache by this point (ok not 100% of cache in the top > output you show, but a fair bit of it). > > Actually I was wrong with "Tweaking login.conf won't help"; you could > reduce the max datasize to something that fits, to protect the machine. > While this won't help actually run the software (in particular a lot > of software really doesn't behave well when malloc fails), it might > help avoid deadlocks. > yes going that route and checking the usage of the DB, clearly the problem here -- -- --------------------------------------------------------------------------------------------------------------------- Knowing is not enough; we must apply. Willing is not enough; we must do
