summaryrefslogtreecommitdiffstats
path: root/contrib/llvm/lib/Bitcode
diff options
context:
space:
mode:
authorwill <will@FreeBSD.org>2015-01-24 17:32:45 +0000
committerwill <will@FreeBSD.org>2015-01-24 17:32:45 +0000
commit2e062600fe2beb07bf5fe1884d91d576a21ce714 (patch)
treeaba62030ace445f000a3241cd0e7b30a14d516fa /contrib/llvm/lib/Bitcode
parentc16f446f6c0823691b1e8f7ab8cbb9084b5d5e7c (diff)
downloadFreeBSD-src-2e062600fe2beb07bf5fe1884d91d576a21ce714.zip
FreeBSD-src-2e062600fe2beb07bf5fe1884d91d576a21ce714.tar.gz
Add vm.panic_on_oom sysctl, which enables those who would rather panic than
kill a process, when the system runs out of memory. Defaults to off. Usually, this is most useful when the OOM condition is due to mismanagement of memory, on a system where the applications in question don't respond well to being killed. 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 than killing the largest process and continuing on its merry way. As kib@ mentions in the differential, there is also protect(1), which uses 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. Differential Revision: D1627 Reviewed by: kib MFC after: 1 week
Diffstat (limited to 'contrib/llvm/lib/Bitcode')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud