OCF_HEARTBEAT_ANYTHI(7)

πŸ’… ocf_heartbeat_anything(7) β€” like, the manual page, but make it make sense

okay so bestie, welcome to the OCF resource agents corner of the internet, this one's OCF_HEARTBEAT_ANYTHI(7) and it's literally the manual page for ocf_heartbeat_anything. yes the title got chopped mid-word, no we're not gonna talk about it πŸŽ€


✨ NAME ✨

ocf_heartbeat_anything β€” manages an arbitrary service. that's it, that's the whole vibe. she's a generalist πŸ‘‘


🌸 SYNOPSIS 🌸

anything [start | stop | monitor | meta-data | validate-all]

like, pick an action, any action. slay.


πŸ¦‹ DESCRIPTION πŸ¦‹

okay so real talk: this is a generic OCF RA (resource agent, keep up πŸ’…) that manages almost anything. not everything β€” almost. she's flexible like that. no cap.


πŸ”₯ SUPPORTED PARAMETERS πŸ”₯

every single one, bestie, we're not skipping a single one. iykyk.

  • binfile β€” the full name of the binary to be executed. heads up though: whatever this is, it's expected to keep running with the same pid β€” it does not just do a thing and bounce. it stays. main character energy only. (required, string, no default 🫢)
  • cmdline_options β€” command line options you wanna pass to the binary. (optional, string, no default)
  • workdir β€” the path from where the binfile will be executed. like, where she gets her start. (optional, string, no default)
  • pidfile β€” file to read/write the PID from/to. (optional, string, default "/var/run/anything_RESOURCE_ID.pid")
  • logfile β€” file to write STDOUT to. (optional, string, default "/dev/null") β€” yes, the default is the void, the void is undefeated πŸ’€
  • errlogfile β€” file to write STDERR to. (optional, string, no default)
  • user β€” user to run the command as. (optional, string, default "root") β€” ngl, root is a lot of power, be responsible bestie πŸ™ˆ
  • monitor_hook β€” command to run in monitor operation. (optional, string, no default)
  • stop_timeout β€” in the stop operation: seconds to wait for kill -TERM to succeed before sending kill -SIGKILL. defaults to 2/3 of the stop operation timeout. so she's polite first, then she's not 😭πŸ”ͺ (optional, string, no default)

πŸ’œ SUPPORTED ACTIONS πŸ’œ

this resource agent supports the following actions (operations), and yes each one has a suggested minimum timeout, write them down:

  1. start β€” starts the resource. suggested minimum timeout: 20s. go bestie go πŸš€
  2. stop β€” stops the resource. suggested minimum timeout: 20s.
  3. monitor β€” performs a detailed status check. suggested minimum timeout: 20s. suggested interval: 10s. she's checking on you every 10 seconds, it's giving concerned bestie πŸ‘€
  4. meta-data β€” retrieves resource agent metadata (internal use only). suggested minimum timeout: 5s.
  5. validate-all β€” performs a validation of the resource configuration. suggested minimum timeout: 5s.

πŸŽ€ EXAMPLE CRM SHELL πŸŽ€

here's what a anything resource looks like using the crm(8) shell, verbatim, do not touch:

primitive p_anything ocf:heartbeat:anything \
  params \
    binfile=string \
  op monitor depth="0" timeout="20s" interval="10s"

🌈 EXAMPLE PCS 🌈

and here's the same deal with pcs(8):

pcs resource create p_anything ocf:heartbeat:anything \
  binfile=string \
  op monitor OCF_CHECK_LEVEL="0" timeout="20s" interval="10s"

note the depth="0" vs OCF_CHECK_LEVEL="0" glow-up β€” different tools, same energy ✨


⭐ SEE ALSO ⭐


πŸ‘‘ AUTHOR πŸ‘‘

ClusterLabs contributors β€” see the resource agent source for information about individual authors. the whole squad, fr fr 🫢


and that's the page!! every flag, every default, every timeout, every example β€” all of it, preserved, no cap πŸ’…

resource-agents UNKNOWN 🌸 dated 10/01/2026 β€” and that's the footer bestie, we made it to the end, OCF_HEARTBEAT_ANYTHI(7) ate and left no crumbs πŸ§šπŸ’–

πŸ“¦ where this page comes from