LIBNUTCLIENT(3)

💖 LIBNUTCLIENT 💖

okay bestie, so this is the libnutclient page from the NUT Manual, section 3 (that's the library section, iykyk). it's giving "high-level client access library for Network UPS Tools" and honestly? iconic.

---

✨ NAME ✨

libnutclient — Network UPS Tools high-level client access library

so like. the whole vibe is: you wanna talk to your UPS without touching any of the gross plumbing. that's her. that's the girl. 🎀

---

🌸 SYNOPSIS 🌸

#include <nutclient.h>

and that's literally it, bestie. no cap. the manpage just says "Refer to this file for more information." — which, okay, rude, but fair, because nutclient.h is where all the actual tea lives. go read her. 📖✨

---

💅 DESCRIPTION 💅

The Network UPS Tools (NUT) nutclient library hands you a whole bunch of genuinely useful functions for programs that wanna chat with upsd(8). she gives you a high-level representation of NUT data through client connection, devices, variables and commands. so instead of you manually wrestling bytes over a socket like some kind of Victorian orphan, she just… handles it. queen behaviour. 👑

and here's the glow-up: unlike upsclient(3) (also known as the "upscli" API), with nutclient all the low-level protocol details are hidden. completely. you never see them. you never think about them. they're not your problem anymore. main character energy fr fr. 🦋

🫶 the state situation

State is maintained across calls in an opaque structure called NUTCLIENT_t. callers are expected to create one per client connection — one girl, one connection, that's the rule 💖 — and these get provided to most of the nutclient functions.

🚨 bestie listen. the format of this structure is subject to change, and client programs must not reference elements within it directly. do not peek inside. do not poke around. she's opaque for a reason. respect her privacy. 🙈

🧚 derived versions

NUTCLIENT_t represents the common connection information. derived versions exist for each connection type — NUTCLIENT_TCP_t for TCP connection. and actually, NUTCLIENT_TCP_t is the unique connection type, so you can just pass NUTCLIENT_TCP_t as a NUTCLIENT_t parameter. convenient?? yes. obsessed?? also yes. ✨

and yeah — see the nutclient.h header for more information. again. she's the source of truth. go say hi. 🌈

---

😭 ERROR HANDLING 😭

There is currently no specific mechanism around error handling.

that's it. that's the whole section. it's giving "we'll figure it out later" and honestly? same. just… be aware, bestie. hold your own hand on this one. 💀

---

⭐ SEE ALSO ⭐

the whole friend group, go follow them all:

• libnutclient_devices(3)
• libnutclient_commands(3)
• libnutclient_general(3)
• libnutclient_misc(3)
• libnutclient_tcp(3)
• libnutclient_variables(3)

---

and that's the page, babe 💖 this was Network UPS Tools 2.8.5, dated 10/07/2026 — go forth, link the library, and slay responsibly. mwah 🎀💅✨