S6-INSTANCE-DELETE(8)

💅 s6-instance-delete — sup girl, this is the s6-instance-delete(8) page from the System Manager's Manual

okay so bestie, buckle up 🎀 because this one's about yeeting an instance into the void, and honestly it's giving "closing a tab you forgot was open" energy.

---

✨ NAME ✨

s6-instance-delete — delete an existing instance of a currently supervised s6-instanced-service(7)

like... it removes an instance. that's the vibe. no cap 🫶

---

🌸 SYNOPSIS 🌸

s6-instance-delete [-X] [-t timeout] servicedir name

---

🦋 DESCRIPTION 🦋

So s6-instance-delete expects a running, supervised s6-instanced-service(7) sitting in servicedir, plus an existing instance of that service named name — and honestly, it does not matter if the instance is up or down, it's getting deleted either way 💀.

It deletes the name instance.

It exits 0. Slay.

s6-instance-delete is similar to s6-svunlink(8), because it uses the same underlying library functions. Under the hood, an instance is a regular service running on a supervision tree that is specific to the instanced service, and s6-instance-delete removes a service directory from that tree. iykyk 🧚

If the template for the service is logged, then s6-instance-delete will delete both the instance and its logger. two for one, literally.

ngl, s6-instance-delete and s6-instance-create(8) are relatively expensive operations, because they have to recursively copy or delete directories and use the s6-ftrigr(7) synchronization mechanism with the instance supervisor. Compare that to s6-instance-control(8), which only has to send commands to already existing supervisors. So if you're gonna turn instances on and off on a regular basis, it is more efficient to keep the instance existing and control it with s6-instance-control(8) than it is to repeatedly create and delete it. bestie, stop doing all that work for no reason 😭

---

💅 OPTIONS 💅

• -X — Don't wait. s6-instance-delete will exit right away, without waiting for the instance (and its supervisor) to properly disappear. ghosting behavior, honestly, but it's allowed 🙈
• -t timeout — If the instance supervisor has not exited after timeout milliseconds, s6-instance-delete will still exit. By default, timeout is 0, which means no time limit. so like, patience is infinite unless you say otherwise ⭐

---

🔥 EXIT STATUS 🔥

• 0 — Success. we love to see it 👑
• 100 — Wrong usage. not me misusing the command 💀
• 111 — System call failed. the system said no and we respect that 🌈

---

🌼 SEE ALSO 🌼

s6-instanced-service(7), s6-instance-control(8), s6-instance-create(8), s6-instance-list(8), s6-instance-maker(8), s6-instance-status(8)

the whole friend group, fr fr 🫶

---

💖 AUTHORS 💖

• Laurent Bercot
• Alexis <flexibeast@gmail.com> (man page port)

---

and that's the whole page, bestie! 🎀 it's from Debian, dated January 11, 2023 — iconic, timeless, and yes it still says S6-INSTANCE-DELETE(8) at the top and bottom because some things are just meant to be. periodt. 💜