shisa_principal_update(3)

📦
version 1.0.3 · 2 versions
  • 1.0.3 · debian bookworm, debian trixie, nixos 26.05, nixpkgs unstable, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking (latest)
  • 1.0.2 · ubuntu jammy
, in debian bookworm, debian trixie, nixos 26.05, nixpkgs unstable, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking

✨ shisa_principal_update — the glow-up edit for your principal data 💅

okay bestie, welcome to shisa_principal_update(3), a page from the shishi manual, section 3 (that's the library-call section, iykyk). it's the API function that lets you edit the deets you've got stored about a principal. no cap.

🌸 NAME 🌸

shisa_principal_update — API function 🎀

🦋 SYNOPSIS 🦋

#include <shisa.h>

int shisa_principal_update(Shisa * dbh, const char * realm, const char *
principal, const Shisa_principal * ph);

like, she takes a handle, a realm, a principal, and a struct pointer, and she returns an int. that's the whole vibe. ⭐

💖 ARGUMENTS 💖

  • Shisa * dbh — the Shisa library handle you got from shisa(). your lil connection to the whole operation, fr fr. 🫶
  • const char * realm — the name of the realm the principal belongs to. where she lives, basically. 🏠
  • const char * principal — the name of the principal you want info about. that's your girl. 👑
  • const Shisa_principal * ph — pointer to an existing principal structure holding the info you want to store in the database. this is the payload, bestie. 📦✨

🌈 DESCRIPTION 🌈

so what she does is modify the information stored about the given principal, and we're talking PRINCIPAL@REALM here — that's the exact format, keep it. 💜

now here's the tea: it's usually a good idea to set only the fields that are to be updated in ph. like, don't dump your whole struct in there if you only changed one thing. that's just messy. 🙈

the generally suggested move is:

  1. first call shisa_principal_find() to grab the current info 📖
  2. then modify one field 🔧
  3. then call shisa_principal_update() ✨
and ngl, modifying several values at once is not recommended in general, because:
  1. it will overwrite any modifications made to other fields between the two calls — by other processes 👀 (yes, other processes are out here editing the same thing, the audacity)
  2. it will cause all values to be written again, which may generate more overhead. extra work for no reason, and we don't do that here 💀

so like... one field at a time, bestie. slow and iconic. 🐢💅

⭐ RETURN VALUE ⭐

  • SHISA_OK — slay, it worked 💖
  • SHISA_NO_REALM — the indicated realm does not exist 😭
  • SHISA_NO_PRINCIPAL — the indicated principal does not exist 😭
  • an error code otherwise — the catch-all, the "something else went down" 🫠

🎀 REPORTING BUGS 🎀

found a bug? don't suffer in silence, report it to <bug-shishi@gnu.org>. 🐛➡️📧

Copyright © 2002-2022 Simon Josefsson.

Copying and distribution of this file, with or without modification, are permitted in any medium without royalty provided the copyright notice and this notice are preserved.

(that's the whole license vibe — keep the notice, keep the notice, and you're golden ✨)

🌟 SEE ALSO 🌟

the full documentation for shishi is maintained as a Texinfo manual. if the info and shishi programs are properly installed at your site, the command

info shishi

should give you access to the complete manual. go read it, it's giving ✨ educated ✨ 🧚

and that's the page, bestie!! 🌈 this was shisa_principal_update(3) from shishi version 1.0.3 — go forth and update responsibly, one field at a time. mwah 💋💖🦋

📦 where this page comes from