OCF_HEARTBEAT_VSFTPD(7)

πŸ’– ocf_heartbeat_vsftpd β€” the manual, but make it a vibe πŸ’–

okay bestie, so this is ocf_heartbeat_vsftpd, and it lives in the OCF resource agents section of your manual pages. yes the one in section 7. we're doing this. πŸ¦‹


✨ NAME ✨

ocf_heartbeat_vsftpd β€” literally just Manages an vsftpd. that's the whole job description. icon behavior honestly. πŸ‘‘


🌸 SYNOPSIS 🌸

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

that's it, that's the lineup. pick your action, girl. πŸ’…


πŸŽ€ DESCRIPTION πŸŽ€

so this script manages vsftpd. simple. elegant. she's a resource agent. 🧚

BUT. and this is the part where you need to lean in β€” there are two things in your vsftpd.conf that HAVE to be right or the whole thing falls apart:

  • the parameter background must be set to yes
  • setproctitle_enable must be disabled

if either of those is off, the RA cannot work. like, at all. not a little bit broken, not working. no cap. 😭 so go fix your config before you come crying to me, bestie.


✨ SUPPORTED PARAMETERS ✨

three little params, all optional, all with defaults so you can just not think about them if you don't want to. 🫢

  • binpath β€” where the vsftpd binary lives. like, for example, "/usr/sbin/vsftpd". (optional, string, default "/usr/sbin/vsftpd")
  • conffile β€” the full path + filename of your vsftpd config file. for example "/etc/vsftpd/vsftpd.conf". (optional, string, default "/etc/vsftpd/vsftpd.conf")
  • pidfile β€” the full path to the vsftpd pidfile. for example "/var/run/vsftpd.pid". (optional, string, default "/var/run/vsftpd.pid")

πŸ’œ SUPPORTED ACTIONS πŸ’œ

this resource agent supports the following actions (operations) β€” aka the things you can actually do:

  • start β€” starts the resource. suggested minimum timeout: 20s.
  • stop β€” stops the resource. suggested minimum timeout: 20s.
  • monitor β€” performs a detailed status check. suggested minimum timeout: 20s. suggested interval: 60s.
  • validate-all β€” performs a validation of the resource configuration. suggested minimum timeout: 20s.
  • meta-data β€” retrieves resource agent metadata (internal use only). suggested minimum timeout: 5s.
ngl meta-data said internal use only and she MEANT it. that's not for you, babe. that's for the machinery. πŸ™ˆ

🌈 EXAMPLE CRM SHELL 🌈

here's what a vsftpd resource looks like when you're configuring it with the crm(8) shell:

primitive p_vsftpd ocf:heartbeat:vsftpd \
  op monitor depth="0" timeout="20s" interval="60s"

copy it, paste it, slay it. ⭐


πŸ“ EXAMPLE PCS πŸ“

and here's the same thing but you're using pcs(8) instead:

pcs resource create p_vsftpd ocf:heartbeat:vsftpd \
  op monitor OCF_CHECK_LEVEL="0" timeout="20s" interval="60s"

see how it's depth="0" in one and OCF_CHECK_LEVEL="0" in the other? yeah. that's a thing. don't mix them up. πŸ’€


πŸ‘‘ SEE ALSO πŸ‘‘


🌸 AUTHOR 🌸

ClusterLabs contributors (see the resource agent source for information about individual authors)


okay that's the whole page!! it's resource-agents version UNKNOWN, dated 04/08/2026, and that's your OCF_HEARTBEAT_VSFTPD(7) moment. go forth and manage that ftp daemon responsibly, mwah πŸ’–βœ¨πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from