fff-config: Set panic on OOM #195

Closed
fbl wants to merge 1 commits from fbl:oom into master
Owner

The OOM killer does not make much sense on a router, because regardless
of which process is killed, most of the time some essential core
functionality is affected.

Set the panic on OOM sysctl, so every OOM leads to a kernel panic and
results in a reboot of the router, which restores a clean state.

Fixes: #131

Signed-off-by: Fabian Bläse fabian@blaese.de

The OOM killer does not make much sense on a router, because regardless of which process is killed, most of the time some essential core functionality is affected. Set the panic on OOM sysctl, so every OOM leads to a kernel panic and results in a reboot of the router, which restores a clean state. Fixes: #131 Signed-off-by: Fabian Bläse <fabian@blaese.de>
fbl added 1 commit 2021-12-30 15:54:59 +01:00
4cb638dad4 fff-config: Set panic on OOM
The OOM killer does not make much sense on a router, because regardless
of which process is killed, most of the time some essential core
functionality is affected.

Set the panic on OOM sysctl, so every OOM leads to a kernel panic and
results in a reboot of the router, which restores a clean state.

Fixes: #131

Signed-off-by: Fabian Bläse <fabian@blaese.de>
Owner

Reviewed-by: Johannes Kimmel <fff@bareminimum.eu>

`Reviewed-by: Johannes Kimmel <fff@bareminimum.eu>`
fbl added this to the 20220405-beta milestone 2022-03-03 15:43:50 +01:00
Author
Owner

Auf meinen staging tree applied.

Auf meinen staging tree applied.
fbl closed this pull request 2022-03-05 19:27:28 +01:00
fbl deleted branch oom 2022-03-05 19:27:31 +01:00

Pull request closed

Sign in to join this conversation.
No description provided.