DLM_STONITH(8)

💖 dlm_stonith(8) — the fencing proxy era 💖

okay bestie, welcome to dlm_stonith, a little manual from the dlm corner of the universe, section 8 (that's the sysadmin section, we love her). she's a proxy for fencing via stonith/pacemaker, and honestly? she's a middlewoman and she's thriving. 🎀

✨ NAME ✨

dlm_stonith — a proxy for fencing via stonith/pacemaker

🦋 SYNOPSIS 🦋

dlm_stonith

that's it. that's the whole vibe. no args in the synopsis, no drama. 💅

🌸 DESCRIPTION 🌸

so here's the tea: dlm_controld can use dlm_stonith as a proxy fence agent when the stonith/pacemaker system is the one doing the actual fencing. like, dlm doesn't fence directly — it hands the job over and dlm_stonith is the go-between. iconic delegation, no notes. 👑

dlm_stonith is run by dlm_controld, and it is not meant to be run manually. bestie, put your hands down, this is not a "let me just try it" situation. 🙈

dlm_controld provides the options on stdin as key=val — that's the real pipeline. command line options are for testing. yes, testing. we all know you're gonna test. 😭

exit code check, because this matters:

• if fencing was successful, this program has a zero exit code ✨
• if fencing failed, this program has a non-zero exit code 💀

🎀 OPTIONS 🎀

• -n nodeid — the nodeid of the target node. the stdin key for this one is "node". (stdin said it first, lowkey.)
• -t fail_time — the time(2) at which the target node failed. if this option is provided, and the last fencing time is later, then a new fencing request is not made. so basically: if we already fenced after the failure, we're not doing it again. no cap, don't re-fence, it's giving unnecessary. 🫶

💜 SEE ALSO 💜

• dlm_controld(8)
• dlm.conf(5)

fr fr, if you're reading this page and thinking "I'll just run it myself", that's a no. let dlm_controld drive. 🚗✨

dlm 🩷 2013-08-01 — that's the source and the date, and that's the whole page, bestie. go forth and proxy responsibly. bye!! 🦋💖🌸