DMMP_PATH_ARRAY_GET(3)

πŸ“¦
version 0.15.1 Β· 3 versions
, in arch rolling, fedora 44, nixos 26.05, nixpkgs unstable, opensuse-leap 16.0

πŸ’– dmmp_path_array_get(3) πŸ’–

okay bestie, welcome to the Device Mapper Multipath API corner of the libdmmp manual ✨ this one's a little function with a big job and honestly? she's giving quiet luxury πŸŽ€


✨ NAME ✨

dmmp_path_array_get β€” Retrieve path pointer array. πŸ¦‹


🌸 SYNOPSIS 🌸

void dmmp_path_array_get (struct dmmp_path_group *dmmp_pg, struct
dmmp_path ***dmmp_ps, uint32_t *dmmp_p_count);

πŸ’… ARGUMENTS πŸ’…

  • dmmp_pg β€” Pointer of 'struct dmmp_path_group'. If this pointer is NULL, your program will be terminated by assert. 😭 yeah she does NOT play about that one.
  • dmmp_ps β€” Output pointer of 'struct dmmp_path' pointer array. If this pointer is NULL, your program will be terminated by assert. πŸ’€ same energy, no exceptions.
  • dmmp_p_count β€” Output pointer of uint32_t. Holds the size of the dmmp_ps pointer array. If this pointer is NULL, your program will be terminated by assert. πŸ™ˆ okay so basically: pass real pointers, all three of them, or catch these asserts.
ngl the vibe check here is brutal but consistent β€” NULL in, terminated out. no cap. 🫢

🧚 DESCRIPTION 🧚

The memory of the output pointer array is held by 'struct dmmp_mpath', so no need to free this memory β€” bestie you do not have to lift a finger πŸ’– the resources will get freed when dmmp_mpath_array_free does its thing. it's giving main character taking care of the cleanup πŸ‘‘


⭐ RETURN ⭐

void β€” that's it, that's the whole return. nothing to catch, nothing to check, she just exists. periodt. ✨


cute lil sign-off time 🌈 this page is from June 2025, documenting dmmp_path_array_get, and it lives in the dmmp_...ay_get(3) corner of the manual. mwah, go read your path groups responsibly πŸ’œπŸŽ€πŸ¦‹