Oracle
1Z0-105 · Question #5
Examine the parameters shown using the sysctl command relating to panic situations: [root@WAYOUT etc]# sysctl -a |grep panic |grep -v hung kernel.panic = 0 kernel.panic_on_oops = 0…
See the full explanation below for the reasoning.
Question
Examine the parameters shown using the sysctl command relating to panic situations: [root@WAYOUT etc]# sysctl -a |grep panic |grep -v hung kernel.panic = 0 kernel.panic_on_oops = 0 kernel.softlockup_panic = 0 kernel.unknown_nmi_panic = 0 kernel.panic_on_unrecovered_nmi = 0 kernel.panic_on_io_nmi = 0 kernel.panic_on_oom = 2 [root@WAYOUT etc]# sysctl -a |grep hung kernel.hung_task_panic = 0 kernel.hung_task_chek_count - 4194304 kernel.hung_task_timeout_secs = 120 kernel.hung_task_warnings = 10 Which two statements are true about system behavior?
Options
- AThe kernel delays panic for a few seconds if a bug is encountered to allow the klogd kernel logging
- BThe kernel panics if a kernel thread sleeps in the TASK_UNINTERRUPTABLE state for more than 120
- CThe kernel attempts to continue if a bug is encountered.
- DThe kernel always panics if an out-of-memory condition arises.
- EThe kernel tries to kill some memory-consuming processes to avoid a panic if an out-of-memory
- FThe kernel panics if a user thread sleeps in the TASK_UNINTERRUPTABLE state for more than 120
Community Discussion
No community discussion yet for this question.