Searched refs:escalate (Results 1 – 8 of 8) sorted by relevance
13 scripts/drbd-demote-or-escalate@.service | 2 +-57 diff --git a/scripts/drbd-demote-or-escalate@.service b/scripts/drbd-demote-or-escalate@.service59 --- a/scripts/drbd-demote-or-escalate@.service60 +++ b/scripts/drbd-demote-or-escalate@.service63 # and then only escalate to FailureAction if that did not help.65 -ExecStart=/lib/drbd/scripts/drbd-service-shim.sh secondary-or-escalate %I66 +ExecStart=@nonarch_libdir@/drbd/scripts/drbd-service-shim.sh secondary-or-escalate %I
13 after that fails to escalate further. This approach gives people more61 events. The cooling off period is voluntary but may escalate to a
617 bool escalate = false; in do_armv7m_nvic_set_pending() local621 escalate = true; in do_armv7m_nvic_set_pending()624 escalate = true; in do_armv7m_nvic_set_pending()627 if (escalate) { in do_armv7m_nvic_set_pending()685 bool escalate = false; in armv7m_nvic_set_pending_lazyfp() local709 escalate = !(fpccr & R_V7M_FPCCR_MMRDY_MASK); in armv7m_nvic_set_pending_lazyfp()712 escalate = !(fpccr & R_V7M_FPCCR_UFRDY_MASK); in armv7m_nvic_set_pending_lazyfp()715 escalate = !(fpccr_s & R_V7M_FPCCR_BFRDY_MASK); in armv7m_nvic_set_pending_lazyfp()718 escalate = !(fpccr_s & R_V7M_FPCCR_SFRDY_MASK); in armv7m_nvic_set_pending_lazyfp()724 if (escalate) { in armv7m_nvic_set_pending_lazyfp()[all …]
267 …8_t esc_blk, uint32_t esc_idx, uint32_t end_data) "END 0x%02x/0x%04x -> escalate END 0x%02x/0x%04x…
55 …nonarch_libdir@#${nonarch_libdir}#g' ${D}${systemd_unitdir}/system/drbd-demote-or-escalate@.service
55 escalate its privileges by directly attacking setuid, setgid, and
180 The need to escalate above mechanism 1 should come with data that captures why188 The need to escalate to 3 would indicate that the BMC's own mechanisms for216 1. The host make use of a timeout to escalate to recovery mechanism 3 as it's328 1. If the `Ready` bit in STR is clear, escalate to recovery mechanism 3.331 2. If the `IBF` bit in STR is set, escalate to recovery mechanism 3. Otherwise,
82 "function" properties can quickly escalate and become hard to write and