9930e738fe
#### Why I did it If a process limits using nodes by mempolicy/cpusets, and those nodes become memory exhaustion status, one process may be killed by oom-killer. No panic occurs in this case, because other node's memory may be free. This means system total status may be not fatal yet. #### How I did it Remove 'vm.panic_on_oom=1' kernel flag from 'vmcore-sysctl.conf ' |
||
|---|---|---|
| .. | ||
| apt | ||
| bash | ||
| config-chassisdb | ||
| config-setup | ||
| constants | ||
| copp | ||
| corefile_uploader | ||
| cron.d | ||
| ebtables | ||
| environment | ||
| fstrim | ||
| hostname | ||
| interfaces | ||
| kdump | ||
| kubernetes | ||
| logrotate | ||
| misc | ||
| monit | ||
| ntp | ||
| pcie-check | ||
| platform | ||
| rsyslog | ||
| secureboot | ||
| snmp | ||
| sudoers | ||
| sysctl | ||
| syslog | ||
| system-health | ||
| systemd | ||
| topology | ||
| updategraph | ||
| warmboot-finalizer | ||
| watchdog-control | ||