semanage_del(3)

💅 semanage_del(3) — the Libsemanage API glow-up

okay bestie, gather round, because we're about to talk about semanage_del, aka the SELinux Management API function that says "girl, bye" to a record in your local store. this is from the Libsemanage API documentation and honestly? it's giving minimal but mighty. ✨

---

🌸 SYNOPSIS 🌸

so the tea is: this delete function works for any semanage record. you just swap in whatever function and object name you actually need — mix and match, it's your world. 🦋

extern int DELETE_FUNCTION (
     semanage_handle_t *handle,
     const semanage_OBJECT_key_t *key);

like, DELETE_FUNCTION and OBJECT are placeholders, bestie. don't come for me, just replace them as necessary. periodt. 💅

---

🎀 DESCRIPTION 🎀

✨ Behavior ✨

the delete function removes the object that matches the key you hand it, straight out of the local store. no match found? no problem, nothing happens, no action is taken, we simply move on with our lives. 🧚

the changes don't actually stick around until you invoke semanage_commit(3) — that's when they become permanent. and lowkey important: additional checks may be performed at that time to make sure the system is left in a valid state. so the commit is the vibe check, basically. 🔥

🫶 Parameters 🫶

• the handle — this is what tracks persistent state across all your semanage calls, and it's also where error reporting happens. it's the main character holding the group chat together, ngl.
• the key — this identifies the data object that's getting deleted from the local store. important detail: the key is a property of the caller, and it will not be stored or modified internally. it does not get kept, it does not get touched. respect its boundaries. 🙈

💜 Requirements 💜

this function has needs, okay:

• it requires a semanage connection to be established — go see semanage_connect(3).
• it must be executed in a transaction — go see semanage_begin_transaction(3).

no connection, no transaction, no delete. it's giving ✨boundaries✨.

---

⭐ RETURN VALUE ⭐

• if it fails, -1 is returned, and the semanage error callback gets invoked to describe the error. so you will know what went wrong, she's not gonna ghost you. 😭
• otherwise, 0 is returned. slay. 🎀

---

🌈 SEE ALSO 🌈

• semanage_handle_create(3)
• semanage_begin_transaction(3)
• semanage_connect(3)
• semanage_commit(3)

---

lowkey reminder bestie: the delete only really lands when you commit. don't forget the semanage_commit(3) or your changes are just vibes. 💀

---

written by ivg2@cornell.edu, dated 16 March 2006, from the semanage_del(3) era of the Libsemanage API docs. she's vintage, she's iconic, she's still serving. 👑💖