CMAP_OVERVIEW(3)

👑 CMAP_OVERVIEW(3) 👑

okay bestie, welcome to the Corosync Cluster Engine Programmer's Manual ✨ this is the lil page that explains the whole vibe before you go deep, so pour ur iced coffee and let's get into it 💖

🌸 NAME 🌸

cmap_overview — the whole entire overview of the Configuration Map, like the trailer before the movie, fr fr

✨ OVERVIEW ✨

So. The CMAP library is what u use to talk to the configuration & statistics databases that corosync runs on. It's giving backstage pass energy 🎀

This library hands u a mechanism to do all of this:

• Create brand new keys 👑
• Change keys that already exist ✨
• Remove keys (rip bozo) 💀
• Iterate keys with a given prefix 🦋
• Track changes on keys, like a little stalker but make it legal 💅

And if ur wondering "okay but what are all these keys even", the description of most keys that corosync itself creates lives in cmap_keys (7). go read it, it's right there 🫶

💀 BUGS 💀

not a single one listed here bestie. the BUGS section is empty. iconic behaviour honestly 🌈

🔥 SEE ALSO 🔥

the whole friend group, no cap:

• cmap_initialize(3)
• cmap_initialize_map(3)
• cmap_finalize(3)
• cmap_get(3)
• cmap_set(3)
• cmap_delete(3)
• cmap_inc(3)
• cmap_dec(3)
• cmap_fd_get(3)
• cmap_dispatch(3)
• cmap_context_set(3)
• cmap_context_get(3)
• cmap_iter_init(3)
• cmap_iter_next(3)
• cmap_iter_finalize(3)
• cmap_track_add(3)
• cmap_track_delete(3)
• cmap_keys(7)

and that's the whole page bestie!! this one came from the corosync Man Page, dated 03/02/2012, and it's the CMAP_OVERVIEW(3) entry 🎀 go slay ur configuration map, u got this 💖✨🦋