Date: Sat, 24 Jan 2015 11:34:10 -0800 From: Garrett Cooper <yaneurabeya@gmail.com> To: Will Andrews <will@FreeBSD.org> Cc: "svn-src-head@freebsd.org" <svn-src-head@freebsd.org>, "svn-src-all@freebsd.org" <svn-src-all@freebsd.org>, "src-committers@freebsd.org" <src-committers@freebsd.org> Subject: Re: svn commit: r277651 - head/sys/vm Message-ID: <AD226C3A-9848-40BE-8912-7695F4367FBE@gmail.com> In-Reply-To: <201501241732.t0OHWkD3089056@svn.freebsd.org> References: <201501241732.t0OHWkD3089056@svn.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Janc 24, 2015, at 09:32, Will Andrews <will@FreeBSD.org> wrote: >=20 > Author: will > Date: Sat Jan 24 17:32:45 2015 > New Revision: 277651 > URL: https://svnweb.freebsd.org/changeset/base/277651 >=20 > Log: > Add vm.panic_on_oom sysctl, which enables those who would rather panic th= an > kill a process, when the system runs out of memory. Defaults to off. >=20 > Usually, this is most useful when the OOM condition is due to mismanageme= nt > of memory, on a system where the applications in question don't respond w= ell > to being killed. >=20 > In theory, if the system is properly managed, it shouldn't be possible to= > hit this condition. If it does, the panic can be more desirable for some > users (since it can be a good means of finding the root cause) rather tha= n > killing the largest process and continuing on its merry way. >=20 > As kib@ mentions in the differential, there is also protect(1), which use= s > procctl(PROC_SPROTECT) to ensure that some processes are immune. However= , > a panic approach is still useful in some environments. This is primarily= > intended as a development/debugging tool. Hi Will! Could you please add a kernel option to set the default from 0 to 1, or p= rovide a tunable so the value could be set in loader.conf? Thanks!=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AD226C3A-9848-40BE-8912-7695F4367FBE>