lsm_acces...tor_delete(3)

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

πŸ’– lsm_access_group_initiator_delete(3) πŸ’–

okay bestie, so this one lives in the Libstoragemgmt C API Manual, and it's literally the glow-down for an initiator β€” we're deleting one from an access group. bye girl πŸ’…


✨ NAME ✨

lsm_access_group_initiator_delete β€” deletes an initiator from an access group πŸšͺπŸ‘‹


🌸 SYNOPSIS 🌸

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

πŸŽ€ ARGUMENTS πŸŽ€

  • conn β€” a valid lsm_connect pointer, no fakes allowed πŸ™…β€β™€οΈ
  • access_group β€” pointer to the lsm_access_group we're modifying. this is the group getting the makeover πŸ’‡β€β™€οΈ
  • initiator_id β€” string. the initiator id that's getting deleted from the group. she's leaving the group chat 😭
  • init_type β€” an lsm_access_group_init_type. the valid initiator types are:
    • 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. ngl bestie the returned value must be freed with lsm_access_group_record_free, don't leave her hanging 🫢
  • flags β€” reserved for future use, must be LSM_CLIENT_FLAG_RSVD. like, no improvising here πŸ™ˆ

⭐ VERSION ⭐

1.0


πŸ’œ DESCRIPTION πŸ’œ

Delete an initiator to the specified access group. that's it, that's the whole vibe β€” she's out πŸ‘‘


🌈 CAPABILITY 🌈

LSM_CAP_ACCESS_GROUP_INITIATOR_DELETE


πŸ”₯ RETURN πŸ”₯

returns an error code as enumerated by lsm_error_number. let's go through the whole roster, no skipping:

  • LSM_ERR_OK
    • on success πŸŽ‰ slay!
  • LSM_ERR_INVALID_ARGUMENT
    • when any argument is NULL, or it's not a valid lsm_connect pointer, or invalid flags, or an invalid lsm_access_group pointer, or an illegal initiator, or an invalid init_type. basically you did something cursed πŸ’€
  • LSM_ERR_NOT_FOUND_ACCESS_GROUP
    • when the access group is not found. she's not here, girl πŸ”
  • LSM_ERR_NO_STATE_CHANGE
    • when the specified initiator is not in the specified access group. so you tried to kick someone who was never in the group in the first place 😭
  • LSM_ERR_LAST_IN_ACCESS_GROUP β€” wait, correction bestie, it's LSM_ERR_LAST_INIT_IN_ACCESS_GROUP
    • when the specified initiator is the last initiator in the specified access group. please use lsm_access_group_delete instead β€” you can't just remove the last one, that's not how this works πŸ™…β€β™€οΈ
  • LSM_ERR_NO_SUPPORT
    • not supported. the server said no 🚫
fr fr, watch out for that LSM_ERR_LAST_INIT_IN_ACCESS_GROUP one β€” if she's the last initiator standing, you gotta call lsm_access_group_delete instead. don't come for the final girl πŸ’…

🫢 SEE ALSO 🫢

lsm_access_group_delete β€” because that's literally the move when you hit the last-initiator situation, iykyk ✨


that's the whole page, bestie β€” February 2026, Libstoragemgmt C API Manual, version 1.0. go delete responsibly πŸ’–πŸ¦‹

πŸ“¦ where this page comes from