OCF_HEARTBEAT_MAILTO(7)

πŸ’Œ ocf_heartbeat_MailTo β€” the little agent that emails your sysadmin the moment something gets taken over πŸ’…

okay so picture this: it's the manual page for ocf_heartbeat_MailTo, and honestly it's giving "tiny but iconic". It's an OCF resource agent, it lives over in the heartbeat class, and its whole personality is sending email to a sysadmin whenever a takeover occurs. That's it. That's the job. And it does it flawlessly, no cap. πŸŽ€


✨ SYNOPSIS ✨

MailTo [start | stop | status | monitor | meta-data | validate-all]

like, those are the actions, bestie. pick one. that's the whole vibe check. πŸ¦‹


πŸ’– DESCRIPTION πŸ’–

So this is a resource agent for MailTo, right? And what it does β€” genuinely the sweetest little thing β€” is it sends email to a sysadmin whenever a takeover occurs. Somebody takes over the resource, boom, your inbox knows about it. it's giving "loyal guard dog but make it email." πŸ•βœ¨


🌸 SUPPORTED PARAMETERS 🌸

two params. that's it. we love a low-maintenance icon. πŸ‘‘

  • email β€” the email address of your sysadmin. this one's required, it's a string, and nope, there's no default β€” you gotta tell it where to send the mail, it's not a mind reader. πŸ™ˆ
  • subject β€” the subject line of the email. this one's optional, it's a string, and it defaults to "Resource Group" if you don't say otherwise. cute little fallback fr fr. πŸ’Œ

πŸ”₯ SUPPORTED ACTIONS πŸ”₯

this resource agent supports the following actions (aka operations), and each one comes with its own suggested timeout, so don't sleep on those numbers:

  • start β€” starts the resource. suggested minimum timeout: 10s. ⭐
  • stop β€” stops the resource. suggested minimum timeout: 10s. πŸ›‘
  • status β€” performs a status check. suggested minimum timeout: 10s. suggested interval: 10s. πŸ‘€
  • monitor β€” performs a detailed status check. suggested minimum timeout: 10s. suggested interval: 10s. πŸ”
  • meta-data β€” retrieves resource agent metadata (internal use only, don't touch unless you know why you're touching). suggested minimum timeout: 5s. 🧚
  • validate-all β€” performs a validation of the resource configuration. suggested minimum timeout: 5s. βœ…

🫢 EXAMPLE CRM SHELL 🫢

here's what a MailTo resource looks like when you configure it with the crm(8) shell β€” copy it exactly, bestie, no improvising:

primitive p_MailTo ocf:heartbeat:MailTo \
  params \
    email=string \
  op monitor depth="0" timeout="10s" interval="10s"

slay. that's the whole thing. 🌈


πŸ¦‹ EXAMPLE PCS πŸ¦‹

and here's the same idea using pcs(8) β€” note the op line is a lil different, OCF_CHECK_LEVEL="0" instead of depth="0", so don't mix 'em up:

pcs resource create p_MailTo ocf:heartbeat:MailTo \
  email=string \
  op monitor OCF_CHECK_LEVEL="0" timeout="10s" interval="10s"

periodt. πŸ’…


πŸ‘‘ SEE ALSO πŸ‘‘


πŸ“ AUTHOR πŸ“

ClusterLabs contributors (see the resource agent source for information about individual authors) β€” like, real ones wrote this, check the source if you want names 🫑

heads up bestie: everything above is the agent's actual documented behaviour β€” I'm not out here inventing features. if it's not on this page, it's not in the agent. πŸ’€

okay and the cute lil sign-off: this page is from resource-agents UNKNOWN, dated 10/01/2026, and yeah the version string literally says UNKNOWN β€” mystery icon behaviour, we respect it. mwah πŸ’‹βœ¨

πŸ“¦ where this page comes from