svup(8)

🌟 svup(8) — the System Manager's Manual check-in bestie 🌟

okay so this is svup(8), straight out of the System Manager's Manual — manual name folded in up here so we’re not copy-pasting that header line, periodt. 💅

💖 NAME 💖

svup — checks whether supervise(8) has started a service.

🌸 SYNOPSIS 🌸

svup [ -L ] [ -l ] service

🦋 DESCRIPTION 🦋

svup checks whether supervise(8) is successfully running in the directory named service, and if it has started the service. If the service includes a log script managed by the same supervise(8), the status of that log is also checked. It’s giving tiny status detective, honestly. 🕵️‍♀️✨

✨ OPTIONS ✨

• -L — if the service includes a log script, check only the log process instead of both. Log-only bestie behavior, no cap.
• -l — do not check if the log is running. Like, skip that little vibe check entirely. 🙈

💅 EXIT CODES 💅

• 0 — it silently exits 0 if supervise(8) is running and the service has been started. No message, no noise, just quiet success. 🫶
• 100 — it silently exits 100 if supervise(8) is not running or the service(s) has not been started. Also silent, but make it “nope.” 💀
• 111 — it exits 111 with a message if an error is encountered. This one actually speaks up. 😭

🌈 ENVIRONMENT 🌈

SUPERVISEDIR

If set, the named directory is used instead of supervise for the status information and control files. If $SUPERVISEDIR is an absolute path, it is suffixed with the path to s with all slashes (/) replaced with colons (:). Keep that s exactly as written, bestie — we don’t “fix” the page. 💖

🎀 SEE ALSO 🎀

• supervise(8)
• svc(8)
• svok(8)
• svstat(8)

💖 signed off from the System Manager's Manual and the svup(8) page — date? the original didn’t stamp one, so I’m not inventing one, periodt. 🫶