lsm_acces...iator_add(3)
π 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 validlsm_connectpointer. like, it has to actually be valid, no fake ones πaccess_groupβ pointer oflsm_access_groupto 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 updatedlsm_access_group. β οΈ the returned value must be freed withlsm_access_group_record_free. don't leave her hanging, free her.flagsβ reserved for future use, must beLSM_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_WWPNLSM_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 isNULLor not a validlsm_connectpointer, or invalid flags, or invalidlsm_access_grouppointer, or illegal initiator, or invalidinit_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_ARGUMENTcatches a lot of sins βNULLstuff, badlsm_connect, bad flags, badlsm_access_group, illegal initiator, badinit_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
- fedora 43: libstoragemgmt-devel 1.10.3-1.fc43 Β· LGPL-2.1-or-later
- fedora 44: libstoragemgmt-devel 1.10.3-1.fc44 Β· LGPL-2.1-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms