lsm_acces...iator_add(3)

πŸ“¦
version 1.10.3 Β· 3 versions
, in fedora 43, fedora 44

πŸ’– lsm_access_group_initiator_add(3) πŸ’–

okay bestie, welcome to the Libstoragemgmt C API Manual ✨ (yes the page header likes to truncate the name into little bits like lsm_acces...iator_add β€” that's just the title being dramatic, the real function is right here 🫢)


🌸 NAME 🌸

lsm_access_group_initiator_add β€” adds an initiator to the access group. that's it, that's the whole job, and she does it flawlessly πŸ’…


✨ SYNOPSIS ✨

int lsm_access_group_initiator_add (lsm_connect *conn, lsm_access_group
*access_group, const char *init_id, lsm_access_group_init_type
init_type, lsm_access_group **updated_access_group, lsm_flag flags);

πŸŽ€ ARGUMENTS πŸŽ€

  • conn β€” a valid lsm_connect pointer. like, it has to actually be valid, no fake ones πŸ™ˆ
  • access_group β€” pointer of lsm_access_group to modify. this is the group getting the glow-up.
  • init_id β€” string. the initiator id to be added to the group. πŸ’«
  • init_type β€” lsm_access_group_init_type. the valid initiator types are, and I cannot stress this enough, exactly these:
    • LSM_ACCESS_GROUP_INIT_TYPE_ISCSI_IQN β€” iSCSI IQN. 🌐
    • LSM_ACCESS_GROUP_INIT_TYPE_WWPN β€” FC WWPN. πŸ”₯
  • updated_access_group β€” output pointer of the updated lsm_access_group. ⚠️ the returned value must be freed with lsm_access_group_record_free. don't leave her hanging, free her.
  • flags β€” reserved for future use, must be LSM_CLIENT_FLAG_RSVD. no improvising, bestie.

⭐ VERSION ⭐

1.0 β€” vintage but iconic, iykyk πŸ‘‘


πŸ¦‹ DESCRIPTION πŸ¦‹

Add an initiator to the specified access group. literally what it says on the tin, and it eats every single time. πŸ“


🌈 CAPABILITY 🌈

  • LSM_CAP_ACCESS_GROUP_INITIATOR_ADD_WWPN
  • LSM_CAP_ACCESS_GROUP_INITIATOR_ADD_ISCSI_IQN

πŸ’€ RETURN πŸ’€

error code as enumerated by lsm_error_number. the whole roster:

  • LSM_ERR_OK β€” on success. slay!! πŸŽ‰
  • LSM_ERR_INVALID_ARGUMENT β€” when any argument is NULL or not a valid lsm_connect pointer, or invalid flags, or invalid lsm_access_group pointer, or illegal initiator, or invalid init_type. so basically: check ur inputs, girl.
  • LSM_ERR_NOT_FOUND_ACCESS_GROUP β€” when the access group is not found. she's not here. 😭
  • LSM_ERR_EXISTS_INITIATOR β€” when the specified initiator is in another access group. not me being two places at once πŸ’€
  • LSM_ERR_NO_STATE_CHANGE β€” when the specified initiator is already in the specified access group. no change, no notes, no drama. πŸ™ˆ
  • LSM_ERR_NO_SUPPORT β€” not supported. 🚫
lowkey reminder: LSM_ERR_INVALID_ARGUMENT catches a lot of sins β€” NULL stuff, bad lsm_connect, bad flags, bad lsm_access_group, illegal initiator, bad init_type. so if something's misbehaving, bestie, look there first πŸ‘€

okay that's the whole page, you ate it up πŸ’–

sign-off moment: this was brought to you by the Libstoragemgmt C API Manual, and the footer stamp says February 2026. take care of urself, free ur lsm_access_group records, and go be the main character of ur own storage array πŸ‘‘βœ¨πŸ«Ά

πŸ“¦ where this page comes from