CMAP_...DELETE(3)

💖 CMAP_TRACK_DELETE — the "actually let's NOT track that anymore" era 💖

okay so bestie, welcome to the Corosync Cluster Engine Programmer's Manual ✨ this one is cmap_track_delete(3), and yes it does exactly what the name says, we're removing stuff, we're unsubscribing, we're closing that tab 🎀

✨ NAME ✨

cmap_track_delete — Remove tracking of values in CMAP 🦋

🌸 SYNOPSIS 🌸

#include <corosync/cmap.h>

cs_error_t cmap_track_delete (cmap_handle_t handle, cmap_track_handle_t
track_handle);

like, two args, one include, that's the whole vibe check 💅

💜 DESCRIPTION 💜

The cmap_track_delte function is used to remove tracking of values changed in CMAP. (yes the page really spells it delte in this one sentence, we are NOT fixing it, it's part of the lore now, iykyk 😭)

The handle argument is connection to CMAP database obtained by calling cmap_initialize(3) function. no cap, you literally cannot be here without that handle, it's your whole ticket in.

The track_handle argument is iterator handle obtained by cmap_track_add(3) function. so you added tracking with cmap_track_add(3), and now you're deleting it with this one. it's giving "we had a moment and now we're moving on" 🧚 it's the natural end of a beautiful tracking arc, periodt.

⭐ RETURN VALUE ⭐

This call returns the CS_OK value if successful. slay! 🎉

CS_ERR_BAD_HANDLE error is returned when track_handle is invalid. aka if you're out here passing a fake handle, the library WILL clock you 💀

🌈 SEE ALSO 🌈

go read these next, they're all icons 👑

• cmap_track_add(3)
• cmap_initialize(3)
• cmap_overview(3)

🫶 and also, the full error menu (collect them all) 🫶

• CS_ERR_TRY_AGAIN — Resource temporarily unavailable. it's not a no, it's a "not right now" bestie 🙈
• CS_ERR_INVALID_PARAM — Invalid argument. that arg was not it ✋
• CS_ERR_ACCESS — Permission denied. you are not on the list, and it's giving velvet rope 😭
• CS_ERR_LIBRARY — The connection failed. the link up did not link up 💔
• CS_ERR_INTERRUPT — System call interrupted by a signal. rude honestly
• CS_ERR_NOT_SUPPORTED — The requested protocol/functionality not supported. not in this house 🚫
• CS_ERR_MESSAGE_ERROR — Incorrect auth message received. the handshake said what now
• CS_ERR_NO_MEMORY — Not enough memory to complete the requested task. she's full, no more room at the inn 🍓

🎀 reminder boo: tracking is a commitment. you call cmap_track_add(3) to start it, you call cmap_track_delete(3) to end it, and you keep your handle and track_handle straight or you get CS_ERR_BAD_HANDLE. that's the whole deal, fr fr.

and that's the page!! mwah 💋 this was the corosync Man Page, dated 06/02/2012 — yes it's vintage, yes it still ate, we stan an older queen 👑 bye bestie, go delete some tracking ✨